Triple
T36843918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rise and fall of Angmar |
E910486
|
entity |
| Predicate | hasStartTimeApprox |
P48368
|
FINISHED |
| Object | Third Age 1300 |
—
|
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: Third Age 1300 | Statement: [rise and fall of Angmar, hasStartTimeApprox, Third Age 1300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartTimeApprox Context triple: [rise and fall of Angmar, hasStartTimeApprox, Third Age 1300]
-
A.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
C.
hasApproximatePublicationStart
Indicates that an entity is associated with an estimated or imprecise starting date for its publication.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
hasPartStartTime
Indicates the time at which a specific part or segment of an entity, event, or process begins.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: May 3, 2026, 4:13 p.m.