Triple
T6087996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPERA |
E135686
|
entity |
| Predicate | reportedFirstTauCandidate |
P51561
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [OPERA, reportedFirstTauCandidate, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedFirstTauCandidate Context triple: [OPERA, reportedFirstTauCandidate, 2010]
-
A.
targetCandidate
Indicates that an entity is being considered or designated as a potential target for selection, action, or further evaluation.
-
B.
firstEncounteredBy
Indicates that one entity is the person or agent who initially discovered, met, or came across the other entity for the first time.
-
C.
firstTestedBy
Indicates that an item, concept, or process was initially tested or tried out by a particular agent or entity.
-
D.
timeOfFirstRevelation
Indicates the specific time at which the first revelation or initial disclosure of something occurred.
-
E.
firstClaimedBy
chosen
Indicates that the referenced entity was the first to assert ownership, discovery, or authorship of 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057a6f7588190b265d6005fbaf6b3 |
completed | March 22, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.