Triple
T36546803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Men |
E901159
|
entity |
| Predicate | lifespanComparedToElves |
P167947
|
FINISHED |
| Object | shorter |
—
|
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: shorter | Statement: [Mortal Men, lifespanComparedToElves, shorter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifespanComparedToElves Context triple: [Mortal Men, lifespanComparedToElves, shorter]
-
A.
averageLifespanComparedTo
chosen
Indicates how the typical lifespan of one entity compares in length to that of another entity.
-
B.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
C.
lifespanType
Indicates the type or category of lifespan associated with an entity, such as whether it is finite, indefinite, or of a particular defined duration.
-
D.
reputedLifespan
Indicates the commonly reported or believed length of time that something is expected to live or remain functional, based on reputation rather than verified measurement.
-
E.
followsLifeSpanOfCharacters
Indicates that one entity’s timeline or progression is structured to track or mirror the life spans of specified characters.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:11 p.m.