Triple
T32097079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foe-hammer |
E819746
|
entity |
| Predicate | laterUsedInAge |
P198963
|
FINISHED |
| Object | Third 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: Third Age | Statement: [Foe-hammer, laterUsedInAge, Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUsedInAge Context triple: [Foe-hammer, laterUsedInAge, Third Age]
-
A.
laterAge
Indicates that one entity is older in age than another entity.
-
B.
laterUsePeriod
chosen
Indicates that one entity is used or becomes relevant after a specified later time period relative to another.
-
C.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
D.
existsInAge
Indicates that an entity is present, valid, or active during a specified age or time period.
-
E.
laterAgeRevision
Indicates that one entity represents a revised age that is later (or updated to a more advanced point in time) than the age specified by 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 1, 2026, 12:26 a.m.