Triple
T26061983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bit-Adini |
E657283
|
entity |
| Predicate | fallDateApproximate |
P116405
|
FINISHED |
| Object | 9th century BCE |
—
|
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: 9th century BCE | Statement: [Bit-Adini, fallDateApproximate, 9th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallDateApproximate Context triple: [Bit-Adini, fallDateApproximate, 9th century BCE]
-
A.
fallApproximateDate
chosen
Indicates that one entity is associated with another by an estimated or imprecise date on which a falling event or decline occurred.
-
B.
fallObserved
Indicates that an instance of a falling event has been detected or recorded as having occurred.
-
C.
fallType
Indicates the specific kind or category of fall that occurred in a falling event.
-
D.
fallSeriesFormat
Indicates that one entity is presented or organized in the specific format used for a fall series (e.g., a seasonal or episodic structure associated with the fall period).
-
E.
fallSeasonChampion
Indicates that the subject is the champion or winner of a competition or league held during the fall season.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60692a4f081909cd9d0ca75d590a0 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:18 p.m.