Triple
T2522638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainforest Alliance |
E55557
|
entity |
| Predicate | usesLabel |
P19697
|
FINISHED |
| Object | Rainforest Alliance Certified seal |
—
|
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: Rainforest Alliance Certified seal | Statement: [Rainforest Alliance, usesLabel, Rainforest Alliance Certified seal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLabel Context triple: [Rainforest Alliance, usesLabel, Rainforest Alliance Certified seal]
-
A.
usedLabel
chosen
Indicates that one entity has applied, assigned, or referenced a particular label to another entity or resource.
-
B.
ownedLabel
Indicates that a label is possessed or controlled by a particular owner or entity.
-
C.
usesIndicator
Indicates that one entity employs or relies on another entity as an indicator, signal, or metric for assessment, decision-making, or interpretation.
-
D.
labelOf
Indicates that one entity serves as the name, tag, or identifying label assigned to another entity.
-
E.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23895348190bb4dad6d7174893a |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.