Triple
T200935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas Fairbanks Jr. |
E4502
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Douglas |
E80
|
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: Douglas | Statement: [Douglas Fairbanks Jr., givenName, Douglas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Douglas Context triple: [Douglas Fairbanks Jr., givenName, Douglas]
-
A.
Douglas
chosen
Douglas is a masculine given name of Scottish origin that has been widely used in English-speaking countries.
-
B.
Montrose
Montrose is a coastal town in eastern Scotland known for its historic harbor, sandy beach, and surrounding nature reserves.
-
C.
Everett
Everett is a surname of English origin borne by various notable individuals, including American politician and orator Edward Everett.
-
D.
Marshall
Marshall is a common English surname borne by numerous notable figures, including military leaders, politicians, and artists.
-
E.
Richardson
Richardson is a suburban city in the Dallas–Fort Worth metropolitan area known for its telecommunications industry and the University of Texas at Dallas.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a37952cbbc8190afd920510408fd31 |
completed | Feb. 28, 2026, 11:25 p.m. |
Created at: Feb. 28, 2026, 2:51 a.m.