Triple
T5350529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas's leaf monkey |
E124165
|
entity |
| Predicate | primarySubstrate |
P16678
|
FINISHED |
| Object | trees |
—
|
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: trees | Statement: [Thomas's leaf monkey, primarySubstrate, trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySubstrate Context triple: [Thomas's leaf monkey, primarySubstrate, trees]
-
A.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
B.
isSubstrateOf
Indicates that one entity serves as the material or reactant upon which another entity (typically an enzyme or process) acts in a chemical or biochemical reaction.
-
C.
substratePreference
chosen
Indicates a relationship where an entity tends to occur on, grow in, or utilize a particular physical material or medium as its preferred substrate.
-
D.
primaryChemicalComponent
Indicates that one entity is the main or predominant chemical substance composing another entity.
-
E.
primaryStructure
Indicates that one entity serves as the main or principal structural component or framework in relation to another entity.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd860fe4048190846a933d0e1b9386 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.