Triple
T637891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelidonium |
E16664
|
entity |
| Predicate | sapCharacteristic |
P662
|
FINISHED |
| Object | acrid yellow latex |
—
|
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: acrid yellow latex | Statement: [Chelidonium, sapCharacteristic, acrid yellow latex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sapCharacteristic Context triple: [Chelidonium, sapCharacteristic, acrid yellow latex]
-
A.
transportCharacteristic
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
-
B.
brandAttribute
Indicates that a specific attribute or characteristic is associated with, or describes, a particular brand.
-
C.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
D.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
E.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a17b125481909a6ab53424954792 |
completed | March 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69a49d0629308190bcc137639567f7c2 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.