Triple
T30478363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pear |
E775504
|
entity |
| Predicate | isCanned |
P169477
|
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, isCanned, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCanned Context triple: [Pear, isCanned, true]
-
A.
isBaked
Indicates that an entity has undergone a baking process, typically by being cooked with dry heat in an oven or similar environment.
-
B.
isCove
Indicates that one location or geographic feature is a small, sheltered bay or inlet along a coastline or shore.
-
C.
inCanonWith
Indicates that two or more works, events, or elements are officially recognized as belonging to the same narrative continuity or canon.
-
D.
isCanonical
Indicates that something represents the standard, authoritative, or officially accepted form within a given context or system.
-
E.
hasCanonization
Indicates that an entity has undergone or been granted formal canonization, typically recognizing it as officially sainted or sanctified.
- 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_69f6871ae044819096fece430cc1f9f9 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:12 p.m.