Triple
T9968125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Wayne |
E195735
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wayne |
E49609
|
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: Wayne | Statement: [Thomas Wayne, familyName, Wayne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wayne Context triple: [Thomas Wayne, familyName, Wayne]
-
A.
Wayne
chosen
Wayne is a masculine given name of English origin commonly used in the United States and other English-speaking countries.
-
B.
Wayne
Wayne is a suburban community in Pennsylvania’s Main Line region, known for its residential neighborhoods and commuter access to Philadelphia.
-
C.
Wayne
Wayne is a suburban township in Passaic County, New Jersey, known for its residential communities, shopping centers, and proximity to New York City.
-
D.
Vaughn
Vaughn is a surname most prominently associated with English film director and producer Matthew Vaughn, known for stylish action and comic-book adaptations.
-
E.
Willis
Willis is a masculine given name and surname of English origin, often considered a variant or cognate of the name Wilson.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb71f9d7c8190ac02c53052c1c6ad |
completed | April 2, 2026, 12:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23db701b881909bb986a32df4349b |
completed | April 5, 2026, 10:47 a.m. |
Created at: March 30, 2026, 8:47 p.m.