Triple
T18453353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir George Godber |
E450840
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | George |
—
|
NE NERFINISHED |
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: George | Statement: [Sir George Godber, givenName, George]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: George Context triple: [Sir George Godber, givenName, George]
-
A.
George
George is the given name of George Patton IV, a U.S. Army general and son of the famed World War II General George S. Patton.
-
B.
George
George is a male given name commonly used in English-speaking countries and borne by numerous historical figures, including kings, presidents, and cultural icons.
-
C.
George
George is a common masculine given name of Greek origin, meaning "farmer" or "earthworker."
-
D.
George
chosen
George is a masculine given name of Greek origin meaning "farmer" or "earthworker," widely used in English-speaking and many other cultures.
-
E.
George
George is the given name of Sir George Grey, a prominent 19th-century British colonial governor and statesman.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264a49ec8190aa43381d93a55e91 |
completed | April 19, 2026, 7 p.m. |
Created at: April 10, 2026, 11:31 a.m.