Triple
T30478365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pear |
E775504
|
entity |
| Predicate | isConsumedWorldwide |
P176337
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pear, isConsumedWorldwide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConsumedWorldwide Context triple: [Pear, isConsumedWorldwide, true]
-
A.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
B.
consumedInCountry
Indicates that something (such as a product, resource, or item) is used up, eaten, or otherwise consumed within the borders of a specified country.
-
C.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
D.
isTypicallyConsumedFrom
Indicates that one entity is most commonly eaten or drunk using, contained in, or taken from the other entity.
-
E.
usedInConstituentCountry
Indicates that something is utilized or applied within a specific constituent country of a larger sovereign state.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 29, 2026, 8:12 p.m.