Triple
T1163094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsuga |
E24536
|
entity |
| Predicate | hasConeOrientation |
P12663
|
FINISHED |
| Object | pendulous seed cones |
—
|
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: pendulous seed cones | Statement: [Tsuga, hasConeOrientation, pendulous seed cones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConeOrientation Context triple: [Tsuga, hasConeOrientation, pendulous seed cones]
-
A.
hasConeType
Indicates that an entity possesses or is associated with a specific type or category of cone.
-
B.
hasOrientation
chosen
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
C.
hasFieldOrientation
Indicates that one entity has a specified directional or spatial orientation relative to a field (such as magnetic, electric, or visual field).
-
D.
coneType
Indicates the specific category or style of cone associated with an entity (e.g., type, shape, or design of the cone).
-
E.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb2bb84819088bd94e91c10fb0c |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.