Triple
T32097078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foe-hammer |
E819746
|
entity |
| Predicate | originAge |
P192650
|
FINISHED |
| Object | First 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: First Age | Statement: [Foe-hammer, originAge, First Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originAge Context triple: [Foe-hammer, originAge, First Age]
-
A.
hasOriginAge
chosen
Indicates that an entity is associated with the age or time period when it first originated or came into existence.
-
B.
estimatedAgeYears
Indicates the approximate number of years assigned as an entity’s age based on estimation rather than exact measurement.
-
C.
oldestAge
Indicates that the associated value represents the greatest (maximum) age within a given group, set, or context.
-
D.
ageAtIntroduction
Indicates the age an entity had at the time it was first introduced or presented in a given context.
-
E.
ageSystem
Indicates a relationship where one entity specifies or uses a particular system or standard for expressing age (e.g., calendar system, counting convention, or age-measurement method) for 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_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
Created at: May 1, 2026, 12:26 a.m.