Triple
T2118729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picea |
E43866
|
entity |
| Predicate | needleAttachment |
P16087
|
FINISHED |
| Object | needles borne singly on pegs |
—
|
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: needles borne singly on pegs | Statement: [Picea, needleAttachment, needles borne singly on pegs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: needleAttachment Context triple: [Picea, needleAttachment, needles borne singly on pegs]
-
A.
needleArrangement
Indicates how needles are positioned or organized relative to each other in a given context.
-
B.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
C.
accessory
Indicates that one entity serves as a supplementary or supporting item to another, often enhancing its function, use, or appearance.
-
D.
annex
Indicates the act of formally incorporating one entity, typically a territory, into the domain or control of another.
-
E.
typeOfFixing
chosen
Indicates the specific method or manner in which one entity is fastened, attached, or secured to another.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb3117c081908c5e748a869d1f9f |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.