Triple
T6161533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Ching |
E137453
|
entity |
| Predicate | earliestStrataDate |
P69130
|
FINISHED |
| Object | late 2nd millennium 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: late 2nd millennium BCE | Statement: [I Ching, earliestStrataDate, late 2nd millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestStrataDate Context triple: [I Ching, earliestStrataDate, late 2nd millennium BCE]
-
A.
earliestDate
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
-
B.
earliestStructuresDateFrom
Indicates that the earliest known structures associated with an entity originate or were first constructed in a specified time period or date.
-
C.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
D.
earliestStage
Indicates that one entity represents the first or minimum stage, phase, or step in a defined ordered sequence relative to another.
-
E.
earliestAttestedStatus
Indicates the earliest known or recorded status that has been documented for an entity.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d371484819090c18b62b095b49e |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:17 p.m.