Triple
T8315611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeremy Ray Taylor |
E194698
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Taylor |
E63210
|
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: Taylor | Statement: [Jeremy Ray Taylor, familyName, Taylor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taylor Context triple: [Jeremy Ray Taylor, familyName, Taylor]
-
A.
Taylor
chosen
Taylor is a common English surname borne by numerous notable individuals across fields such as politics, arts, sports, and academia.
-
B.
Taylor
Taylor is a suburban city in Wayne County, Michigan, known for its residential communities and proximity to Detroit.
-
C.
Tyler
Tyler is the officer in a Masonic lodge responsible for guarding the entrance and ensuring only qualified individuals are admitted to meetings.
-
D.
Tyler
Tyler is a fictional character appearing in the American television series "Kristin."
-
E.
Tyler
Tyler is a masculine given name commonly used in English-speaking countries, originally derived from an occupational surname meaning "tile maker" or "house builder."
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f540b2081908ccb1b2ed040c74e |
completed | March 31, 2026, 8:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd9583fa8081909778288f4c96de72 |
completed | April 1, 2026, 10 p.m. |
Created at: March 30, 2026, 5:55 p.m.