Triple
T1223323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tommy Atkins mango |
E26271
|
entity |
| Predicate | hasYield |
P26004
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Tommy Atkins mango, hasYield, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYield Context triple: [Tommy Atkins mango, hasYield, high]
-
A.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
B.
hasRemainsOf
Indicates that one entity physically contains, preserves, or is associated with the leftover physical traces or remnants of another entity.
-
C.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
D.
hasSeeding
Indicates that an entity is assigned or associated with a specific seeding position or rank, typically for ordering or placement in a competitive or structured context.
-
E.
hasToDoWith
Indicates a general, non-specific relationship or association between entities, suggesting they are related, connected, or relevant to each other in some way.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be233fd88190996faf4105c0b8d7 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd3140688190ac6e24de157fd61e |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:47 p.m.