Triple
T32097906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archelaus |
E819767
|
entity |
| Predicate | laterServedUnder |
P200301
|
FINISHED |
| Object | Lucius Licinius Lucullus |
—
|
NE NERFINISHED |
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: Lucius Licinius Lucullus | Statement: [Archelaus, laterServedUnder, Lucius Licinius Lucullus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterServedUnder Context triple: [Archelaus, laterServedUnder, Lucius Licinius Lucullus]
-
A.
laterServedBy
Indicates that one entity is subsequently served or provided service by another entity at a later time.
-
B.
laterServedIn
Indicates that one entity subsequently held a service position or role in which another entity had previously served.
-
C.
laterServedWith
Indicates that one entity was served or presented after another entity, in a subsequent course or sequence.
-
D.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
E.
isServedAfter
Indicates that one event, item, or course is provided or occurs later in sequence than another.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69ff7fc715208190a8e4e2cc5aa72d2c |
completed | May 9, 2026, 6:41 p.m. |
Created at: May 1, 2026, 12:26 a.m.