Triple
T37544491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex Ryan’s 3–4 attacking defense |
E933419
|
entity |
| Predicate | coverageConcepts |
P153106
|
FINISHED |
| Object | Cover 1 |
—
|
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: Cover 1 | Statement: [Rex Ryan’s 3–4 attacking defense, coverageConcepts, Cover 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverageConcepts Context triple: [Rex Ryan’s 3–4 attacking defense, coverageConcepts, Cover 1]
-
A.
commonConcept
Indicates that two or more entities share the same underlying idea, notion, or conceptual meaning.
-
B.
detailsConcept
chosen
Indicates that one entity provides additional information, clarification, or elaboration about a concept represented by another entity.
-
C.
protectedConcept
Indicates that one entity is a concept or attribute that is legally or normatively safeguarded from discrimination, harm, or unauthorized use in relation to another entity.
-
D.
expandsConcept
Indicates that one concept broadens, elaborates, or adds detail to the meaning or scope of another concept.
-
E.
usesConceptIdentifier
Indicates that one entity refers to or operates with a specific concept by means of its unique identifier.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:17 p.m.