Triple
T9032899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luc Longley |
E216416
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Longley |
E220449
|
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: Longley | Statement: [Luc Longley, familyName, Longley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longley Context triple: [Luc Longley, familyName, Longley]
-
A.
Longley
chosen
Longley is a surname most notably associated with Luc Longley, the Australian former professional basketball player and three-time NBA champion with the Chicago Bulls.
-
B.
Hockley
Hockley is a village in Essex, England, known for its residential character and rail links to London and Southend.
-
C.
Hockley
Hockley is a vibrant, historic district in Nottingham, England, known for its independent shops, bars, and creative cultural scene.
-
D.
Bramley
Bramley is a village in Surrey, England, known for its historic buildings and rural character within the Borough of Waverley.
-
E.
Hordley
Hordley is a small rural settlement located in the parish of St. Thomas in the East, Jamaica.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6aa0c89c81909792190f08fef8df |
completed | April 1, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfdbc9c6e08190aa71d84316afc6d5 |
completed | April 3, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:08 p.m.