Triple
T1044701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delos |
E22549
|
entity |
| Predicate | politicalStatusInAntiquity |
P23875
|
FINISHED |
| Object | religious center |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: religious center | Statement: [Delos, politicalStatusInAntiquity, religious center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusInAntiquity Context triple: [Delos, politicalStatusInAntiquity, religious center]
-
A.
governedInAntiquityBy
Indicates that one entity exercised political rule or authority over another entity during ancient or classical historical periods.
-
B.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
-
C.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
D.
legalStatusOfSlavery
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
E.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b84937688190a5899af2104002df |
completed | March 1, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8444f708190815732408aa0463e |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.