Triple
T28551273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Muster |
E722890
|
entity |
| Predicate | dateReachedNo1 |
P119090
|
FINISHED |
| Object | 1996-02-12 |
—
|
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: 1996-02-12 | Statement: [Thomas Muster, dateReachedNo1, 1996-02-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateReachedNo1 Context triple: [Thomas Muster, dateReachedNo1, 1996-02-12]
-
A.
hasReach
Indicates that one entity is able to extend its influence, access, or physical span to another entity or area.
-
B.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
C.
reachedWorldNo
chosen
Indicates that an entity has attained a specified world ranking position (e.g., world number X) in a particular domain or classification.
-
D.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
E.
hasReachUnit
Indicates that one entity uses a specified unit of measurement to express its reach or extent.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:42 a.m.