Triple
T29022451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hegesinus of Pergamon |
E737489
|
entity |
| Predicate | followsInOffice |
P186460
|
FINISHED |
| Object | Carneades of Cyrene |
—
|
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: Carneades of Cyrene | Statement: [Hegesinus of Pergamon, followsInOffice, Carneades of Cyrene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInOffice Context triple: [Hegesinus of Pergamon, followsInOffice, Carneades of Cyrene]
-
A.
hasRelativeInOffice
Indicates that one entity has a family member who holds or held a particular office or official position.
-
B.
inOfficeDuring
Indicates that an entity holds or occupies an office or position throughout a specified time period.
-
C.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
D.
mentionsOffice
Indicates that one entity explicitly refers to or brings up an office (such as a workplace, office location, or office role) in relation to another entity.
-
E.
representsInOffice
Indicates that one entity serves as an official representative of another entity within a specific office, position, or institutional role.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 28, 2026, 9:50 a.m.