Triple
T35386234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invincibility Leaf |
E1022799
|
entity |
| Predicate | relatedToItem |
P70956
|
FINISHED |
| Object | Super Leaf |
E311685
|
NE 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: Super Leaf | Statement: [Invincibility Leaf, relatedToItem, Super Leaf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToItem Context triple: [Invincibility Leaf, relatedToItem, Super Leaf]
-
A.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
associatedItem
chosen
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
-
C.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
D.
relatedToPart
Indicates that one entity has a connection or association with a specific part or component of another entity.
-
E.
relatedToProduct
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
- F. None of above.
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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836aaa78c8190851152c4262004cd |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.