Triple
T2666631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Taylor |
E55650
|
entity |
| Predicate | selectedAllPro |
P41544
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Jason Taylor, selectedAllPro, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedAllPro Context triple: [Jason Taylor, selectedAllPro, true]
-
A.
selectedTo
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
B.
selectionFrom
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
-
C.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
D.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
E.
allMembersAre
Indicates that every member of a specified group or set satisfies a given condition or belongs entirely to another specified group.
- F. None of above. chosen
Provenance (4 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd97040e48190b0a87489f108810e |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.