Triple
T7227844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Wyly |
E154826
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wyly |
E618172
|
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: Wyly | Statement: [Charles Wyly, familyName, Wyly]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wyly Context triple: [Charles Wyly, familyName, Wyly]
-
A.
Wyly
chosen
Wyly is a surname most prominently associated with the American billionaire entrepreneur and philanthropist family led by brothers Sam and Charles Wyly.
-
B.
Wylie
Wylie is a suburban city in the Dallas–Fort Worth metropolitan area in northeastern Texas.
-
C.
Kinsealy
Kinsealy is a suburban locality in north County Dublin, Ireland, known for its residential character and proximity to Swords and Dublin city.
-
D.
Wyot
Wyot is a medieval given name that served as an earlier form of the modern English name Wyatt.
-
E.
Wilsede
Wilsede is a small village in the Lüneburg Heath region of Lower Saxony, Germany, known for its well-preserved heathland landscape and traditional car-free character.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9df72cc81908d1c04e6e310fbb4 |
completed | March 27, 2026, 8:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cc1cdfb88190934387e44531b732 |
completed | March 28, 2026, 12:39 p.m. |
Created at: March 27, 2026, 2:54 p.m.