Triple
T12128585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodney Crowell |
E288873
|
entity |
| Predicate | familyName |
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: [Rodney Crowell, familyName, Crowell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Crowell Context triple: [Rodney Crowell, familyName, 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.
Bivins
Bivins is a surname most notably associated with Michael Bivins, an American singer, rapper, and music executive known for his work with New Edition and Bell Biv DeVoe.
-
D.
Wylie
Wylie is a suburban city in the Dallas–Fort Worth metropolitan area in northeastern Texas.
-
E.
Crawford
Crawford is a small community located within Russell County, likely serving as one of its local residential or rural settlements.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9157ce6b88190b16592cc48244db3 |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f68ac15c81908388dd3194e9dfc4 |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:49 p.m.