Triple
T27119698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLL Cup |
E686960
|
entity |
| Predicate | isTangibleObject |
P40629
|
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: [NLL Cup, isTangibleObject, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTangibleObject Context triple: [NLL Cup, isTangibleObject, true]
-
A.
isPhysicalArtifact
chosen
Indicates that the subject is a tangible, man-made object that physically exists in the real world.
-
B.
canBeHeld
Indicates that an entity is capable of being physically grasped, supported, or carried by another entity.
-
C.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
D.
isResonantObject
Indicates that one entity functions as an object capable of resonating (physically or metaphorically) in response to another entity or influence.
-
E.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
- F. None of above.
Provenance (3 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624421d188190a5356a4596df536e |
completed | May 2, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:58 a.m.