Triple
T11977633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocos nucifera |
E285075
|
entity |
| Predicate | sapUse |
P102684
|
FINISHED |
| Object | toddy production |
—
|
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: toddy production | Statement: [Cocos nucifera, sapUse, toddy production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sapUse Context triple: [Cocos nucifera, sapUse, toddy production]
-
A.
sap
Indicates the act of gradually weakening, draining, or undermining the strength, energy, or effectiveness of someone or something.
-
B.
sapType
Indicates the specific category or classification of SAP-related type assigned to an entity within a system or data model.
-
C.
sapContains
Indicates that one entity spatially or logically contains another as a part, component, or subset within its bounds.
-
D.
servicePlatform
Indicates that one entity functions as a platform or environment through which services are provided, managed, or delivered to another entity.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- F. None of above. chosen
Provenance (4 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.