Triple
T11049194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gladden Fields |
E261202
|
entity |
| Predicate | eventDateAge |
P51855
|
FINISHED |
| Object | Third Age |
—
|
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 | Statement: [Gladden Fields, eventDateAge, Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateAge Context triple: [Gladden Fields, eventDateAge, Third Age]
-
A.
containsAge
chosen
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
B.
ageDetail
Indicates a detailed specification of an entity’s age, such as exact value, range, or related age attributes.
-
C.
ageInPlay
Indicates that an entity’s age is relevant or applicable within the context of a particular play, game, or interactive scenario.
-
D.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
E.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79867fa28819094f564273e3ef51d |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.