Triple
T1272655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metasequoia |
E15743
|
entity |
| Predicate | describedAsLivingFossil |
P28258
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Metasequoia, describedAsLivingFossil, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsLivingFossil Context triple: [Metasequoia, describedAsLivingFossil, true]
-
A.
containsFossilsOf
Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
-
B.
fossilRecordExtendsBackTo
Indicates that the existence or presence of something is documented in the fossil record as originating from a specified time or geological period.
-
C.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
-
D.
hasLivingSpecies
Indicates that an entity currently contains, supports, or is associated with one or more species that are alive or extant.
-
E.
stateFossil
Indicates that a particular fossil has been officially designated as the representative state fossil of a given state.
- F. None of above. chosen
Provenance (4 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c31400c08190a07ccb736df3bf54 |
completed | March 1, 2026, 10:52 p.m. |
Created at: March 1, 2026, 7:50 p.m.