Triple
T11309973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kuni no miyatsuko |
E267811
|
entity |
| Predicate | timeInception |
P13526
|
FINISHED |
| Object | 3rd century |
—
|
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: 3rd century | Statement: [kuni no miyatsuko, timeInception, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInception Context triple: [kuni no miyatsuko, timeInception, 3rd century]
-
A.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
B.
inceptionTime
chosen
Indicates the specific point in time when an entity, event, or relationship begins or is first established.
-
C.
endTimeInGenesis
Indicates the time at which an event or state concludes within the temporal framework defined by the Genesis context or system.
-
D.
timeOfAppearance
Indicates the specific time at which an entity or event becomes visible, present, or first occurs.
-
E.
startTimeInGenesis
Indicates the point in time at which an event or process begins within the context of the Genesis narrative or dataset.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c0b3b88190ac0e3d6a5ad3b9bc |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.