Triple
T7499257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Su Rogers |
E177216
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Rogers |
E773
|
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: Rogers | Statement: [Su Rogers, hasFamilyName, Rogers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rogers Context triple: [Su Rogers, hasFamilyName, Rogers]
-
A.
Rogers
chosen
Rogers is a common English-language surname borne by numerous notable individuals across fields such as science, politics, entertainment, and sports.
-
B.
Rogers
Rogers is a major Canadian communications and media company known for its wireless, cable, internet, and sports media services.
-
C.
Rogers
Rogers is a growing city in northwestern Arkansas known for its role in the Fayetteville–Springdale–Rogers metropolitan area and as a regional commercial and retail hub.
-
D.
Rogers
Rogers is a small suburban city in Minnesota known for its location northwest of Minneapolis and its blend of residential neighborhoods, light industry, and retail development.
-
E.
Rogers & Wells
Rogers & Wells was a prominent New York-based law firm known for its corporate and international legal practice before merging into Clifford Chance in 2000.
- 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_69c69f2696688190915a8458f2398211 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f597a0c08190b34fa283a11d98c7 |
completed | March 27, 2026, 9:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c84608021481908ce58a131d75188b |
completed | March 28, 2026, 9:20 p.m. |
Created at: March 27, 2026, 3:44 p.m.