Triple
T10530668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George M. Low |
E248432
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | George |
E685754
|
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: George | Statement: [George M. Low, givenName, George]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: George Context triple: [George M. Low, givenName, George]
-
A.
George
George is the heroic protagonist of the fantasy film "The Magic Sword," known for embarking on a perilous quest to rescue a princess from an evil sorcerer.
-
B.
George
George is a common English surname of likely Greek and Latin origin, associated with numerous notable historical and contemporary figures.
-
C.
George
George is the given name of George Murray, 6th Duke of Atholl, a Scottish peer and nobleman of the 19th century.
-
D.
George
chosen
George is the given name of George de Hevesy, the Hungarian radiochemist and Nobel laureate known for pioneering the use of radioactive tracers in studying chemical processes.
-
E.
George
George is a supporting character in the romantic comedy film "27 Dresses," serving as a colleague and love interest within the story’s central wedding-planning world.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a16915c8190ac4f3fd5e43c5fed |
completed | April 7, 2026, 1:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d933fffc4c81908798094f72a06d18 |
completed | April 10, 2026, 5:31 p.m. |
Created at: April 6, 2026, 12:30 p.m.