Triple
T20650996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL DROY |
E507491
|
entity |
| Predicate | positionScope |
P61710
|
FINISHED |
| Object | defensive players only |
—
|
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: defensive players only | Statement: [NFL DROY, positionScope, defensive players only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionScope Context triple: [NFL DROY, positionScope, defensive players only]
-
A.
locationScope
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
B.
scopeOfReference
chosen
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
-
C.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
D.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
E.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
- F. None of above.
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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af21e87c8190835bf2b2ef195626 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.