Triple
T37665104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outer End islands |
E937802
|
entity |
| Predicate | plantSignificance |
P183631
|
FINISHED |
| Object | only natural source of chorus fruit |
—
|
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: only natural source of chorus fruit | Statement: [Outer End islands, plantSignificance, only natural source of chorus fruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantSignificance Context triple: [Outer End islands, plantSignificance, only natural source of chorus fruit]
-
A.
botanicalSignificance
chosen
Indicates the importance or relevance of one entity to another in a botanical or plant-related context.
-
B.
famousPlants
Indicates that the plants in question are widely known or celebrated, typically for their distinctive characteristics, history, or cultural significance.
-
C.
plantSymbolism
Indicates that a plant is associated with a particular symbolic meaning, concept, or value.
-
D.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
E.
hasEconomicImportanceFor
Indicates that one entity holds economic value, benefit, or significance for 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e001c88190912781fa9a84f246 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.