Triple
T37895986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PFWA All-NFC Team |
E945278
|
entity |
| Predicate | positionCoverage |
P201534
|
FINISHED |
| Object | quarterback |
—
|
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: quarterback | Statement: [PFWA All-NFC Team, positionCoverage, quarterback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionCoverage Context triple: [PFWA All-NFC Team, positionCoverage, quarterback]
-
A.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
B.
stageCoverage
Indicates that one entity provides or has coverage, representation, or support for another within a particular stage or phase of a process or workflow.
-
C.
projectionCoverage
Indicates the extent to which one entity’s projection or mapping spans, includes, or accounts for another entity or domain.
-
D.
edgeCoverage
Indicates that one element (such as a test, path, or configuration) covers or exercises a specific edge or connection in a graph or network structure.
-
E.
segmentCovered
Indicates that one segment or portion of something is fully or partially covered or spanned by another.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_6a000013004c8190a01710441f881fdc |
completed | May 10, 2026, 3:48 a.m. |
Created at: May 3, 2026, 4:19 p.m.