Triple
T9882915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laysan albatross |
E180854
|
entity |
| Predicate | maximumLongevity |
P49304
|
FINISHED |
| Object | over 60 years |
—
|
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: over 60 years | Statement: [Laysan albatross, maximumLongevity, over 60 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumLongevity Context triple: [Laysan albatross, maximumLongevity, over 60 years]
-
A.
maximumRecordedLifespan
chosen
Indicates the greatest length of time that has ever been recorded for an individual of a given type to live.
-
B.
maximumLifetimeBenefit
Indicates the greatest total amount of benefit that can be received over the entire duration of eligibility or coverage.
-
C.
maximumAgeMa
Indicates that there is a specified maximum age limit applicable to an entity or relationship.
-
D.
longestDurationAt
Indicates that one entity has the greatest length of time associated with a particular state, event, or activity compared to other relevant entities.
-
E.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb418417c8190b00dea8916a2e102 |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:38 p.m.