Triple
T1192527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Frick |
E25393
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Frick |
E5200
|
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: Frick | Statement: [Ford Frick, familyName, Frick]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Frick Context triple: [Ford Frick, familyName, Frick]
-
A.
Frick
chosen
Frick is a surname most prominently associated with American industrialist and art patron Henry Clay Frick.
-
B.
Reinsdorf
Reinsdorf is a surname most prominently associated with American sports team owner Jerry Reinsdorf, known for owning the Chicago Bulls and Chicago White Sox.
-
C.
Flinck
Flinck is a Dutch surname most notably associated with the 17th-century painter Govert Flinck, a prominent figure of the Dutch Golden Age.
-
D.
Wayne
Wayne is a masculine given name of English origin commonly used in the United States and other English-speaking countries.
-
E.
Lamon
Lamon is an archaeological site notable for inscriptions in the ancient Venetic language.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd761ef08190b431b80f326d1ab2 |
completed | March 1, 2026, 10:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac7f36371c8190a656463a9ae6402a |
completed | March 7, 2026, 7:40 p.m. |
Created at: March 1, 2026, 7:45 p.m.