Triple
T20191501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulborb |
E492987
|
entity |
| Predicate | sizeRelativeToPikmin |
P139071
|
FINISHED |
| Object | much larger than Pikmin |
—
|
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: much larger than Pikmin | Statement: [Bulborb, sizeRelativeToPikmin, much larger than Pikmin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeRelativeToPikmin Context triple: [Bulborb, sizeRelativeToPikmin, much larger than Pikmin]
-
A.
plantSize
Indicates the relative physical magnitude or dimensions of a plant, such as how large or small it is.
-
B.
relativeFruitSize
Indicates the comparative size relationship between one fruit and another (e.g., larger than, smaller than, or similar in size).
-
C.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
D.
leafSize
Indicates the size or dimensions of a leaf in relation to a plant or tree.
-
E.
relativeSizeInArchipelago
Indicates the comparative size relationship of an entity relative to other entities within the same archipelago.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad593f88190a1e534fed38b3cd7 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:37 p.m.