Triple
T27766374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Dai |
E701610
|
entity |
| Predicate | heldByBeforeYear |
P163228
|
FINISHED |
| Object | 180 BC |
—
|
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: 180 BC | Statement: [Prince of Dai, heldByBeforeYear, 180 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByBeforeYear Context triple: [Prince of Dai, heldByBeforeYear, 180 BC]
-
A.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
B.
yearHeld
Indicates the specific year during which an event, position, or status was held or took place.
-
C.
formedBeforeYear
Indicates that an entity was formed or came into existence earlier than a specified calendar year.
-
D.
hasBeenHeldBy
Indicates that an entity has previously possessed, controlled, or occupied another entity for some duration in the past.
-
E.
hasPreviouslyBeenHeldIn
Indicates that an entity was located, confined, or kept in a particular place or container at some time in the past.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637939be0819082653d4115cd1be1 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:31 p.m.