Triple
T34637752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wimbledon gentlemen’s singles title 1887 |
E889475
|
entity |
| Predicate | hadChallengeRound |
P179725
|
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: [Wimbledon gentlemen’s singles title 1887, hadChallengeRound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadChallengeRound Context triple: [Wimbledon gentlemen’s singles title 1887, hadChallengeRound, true]
-
A.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
B.
laterChallengedBy
Indicates that an earlier claim, decision, or position was subsequently questioned, disputed, or opposed by another party.
-
C.
hasBeenChallengedFor
Indicates that an entity has been formally questioned, disputed, or contested specifically in relation to another entity or issue.
-
D.
hasBeenChallengedIn
Indicates that an entity has faced a challenge, contest, or dispute within a specified context, domain, or setting.
-
E.
usedToChallenge
Indicates that one entity was employed or relied upon by another as a means to confront, contest, or question something or someone.
- F. None of above. chosen
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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:04 a.m.