Triple
T24053795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle at Delphi |
E595737
|
entity |
| Predicate | finalSuppressionCenturyAD |
P58449
|
FINISHED |
| Object | 4th century AD |
—
|
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: 4th century AD | Statement: [Oracle at Delphi, finalSuppressionCenturyAD, 4th century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSuppressionCenturyAD Context triple: [Oracle at Delphi, finalSuppressionCenturyAD, 4th century AD]
-
A.
suppressionCentury
chosen
Indicates the century during which a suppression, prohibition, or forcible halting of something took place.
-
B.
supersededInCentury
Indicates that one entity has been replaced or rendered obsolete by another during a specified century.
-
C.
activeUntilCentury
Indicates that an entity remains active or in effect up to and including a specified century.
-
D.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
E.
ruledUntilCentury
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) a specified century.
- F. None of above.
Provenance (3 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d4325c819080b878fe77280947 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:21 p.m.