Triple
T294981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cup |
E6072
|
entity |
| Predicate | professionalUseSince |
P2451
|
FINISHED |
| Object | 1926 |
—
|
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: 1926 | Statement: [The Cup, professionalUseSince, 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionalUseSince Context triple: [The Cup, professionalUseSince, 1926]
-
A.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
B.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
C.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
D.
inUseSince
chosen
Indicates that an entity has been actively in use starting from a specified point in time.
-
E.
professional
Indicates that one entity has a formal, occupation-related role, service, or expertise in relation to 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.