Triple
T20834766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comorian people |
E512929
|
entity |
| Predicate | traditionalExport |
P15641
|
FINISHED |
| Object | ylang-ylang |
—
|
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: ylang-ylang | Statement: [Comorian people, traditionalExport, ylang-ylang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalExport Context triple: [Comorian people, traditionalExport, ylang-ylang]
-
A.
traditionalTrade
Indicates a relationship where goods or services are exchanged using long-established, customary methods rather than modern or digital trading systems.
-
B.
traditionalOrigin
chosen
Indicates that something comes from, or is rooted in, a long-established cultural or customary source or practice.
-
C.
traditionalBase
Indicates that one entity serves as the customary or historically established foundation or basis for another.
-
D.
traditionalOrder
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
E.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c32622c481908b8d2159bd5bb0ad |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:42 p.m.