Triple
T13372298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McX |
E319094
|
entity |
| Predicate | contrastedWith |
P278
|
FINISHED |
| Object | Wyman |
E319093
|
NE 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: Wyman | Statement: [McX, contrastedWith, Wyman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wyman Context triple: [McX, contrastedWith, Wyman]
-
A.
Wyman
chosen
Wyman is a character appearing in Willard Van Orman Quine’s philosophical essay “On What There Is,” used to illustrate issues in ontology and the problem of non-existent objects.
-
B.
Wyman-Gordon
Wyman-Gordon is an industrial manufacturer known for producing high-strength forged components, particularly for the aerospace and energy industries.
-
C.
Twyman
Twyman is a surname most notably associated with Jack Twyman, an American Basketball Hall of Famer and longtime NBA star for the Cincinnati Royals.
-
D.
Welchman
Welchman is a surname most notably associated with Gordon Welchman, a key British codebreaker at Bletchley Park during World War II.
-
E.
Lawmond
Lawmond is a Scottish family name recognized as a sept of Clan Lamont, a historic Highland clan from Argyll.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd8950481909785a2060f43b6ed |
completed | April 11, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f72682c7f08190b8553ca22734df27 |
completed | May 3, 2026, 10:42 a.m. |
Created at: April 9, 2026, 9:33 p.m.