Triple
T5594147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Crowell |
E146952
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Crowell |
E146952
|
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: Crowell | Statement: [John Crowell, hasSurname, Crowell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Crowell Context triple: [John Crowell, hasSurname, Crowell]
-
A.
Crowell
chosen
Crowell is a surname of English origin that is a variant of the name Crowe.
-
B.
Eldridge
Eldridge is an English-language surname of Old English origin, borne by various notable individuals across fields such as politics, the arts, and sports.
-
C.
Wylie
Wylie is a suburban city in the Dallas–Fort Worth metropolitan area in northeastern Texas.
-
D.
Crawford
Crawford is a Scottish-origin surname borne by numerous notable figures across politics, sports, arts, and entertainment.
-
E.
Blakely
Blakely is a given name and surname of English origin that has become popular as a modern unisex first name.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020bc41408190bc990da8ddeb931e |
completed | March 22, 2026, 5:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07d8c6f8881909ac2018d11f5aef8 |
completed | March 22, 2026, 11:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.