Triple
T36545475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Marshes |
E901128
|
entity |
| Predicate | timePeriodFormed |
P193442
|
FINISHED |
| Object | Second Age |
—
|
NE NERFINISHED |
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: Second Age | Statement: [Dead Marshes, timePeriodFormed, Second Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodFormed Context triple: [Dead Marshes, timePeriodFormed, Second Age]
-
A.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodQualifier
Indicates how a time-related statement or value is further specified or constrained, such as by defining its scope, phase, or contextual condition within a broader time period.
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
timePeriodImplied
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: May 3, 2026, 4:11 p.m.