Triple
T7214561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 NFC Championship Game |
E149497
|
entity |
| Predicate | pointsHomeTeam |
P75473
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [1981 NFC Championship Game, pointsHomeTeam, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsHomeTeam Context triple: [1981 NFC Championship Game, pointsHomeTeam, 20]
-
A.
goalsHomeTeam
Indicates the number of goals scored by the home team in a match.
-
B.
locationTeam1Home
Indicates that the specified location serves as the home venue or home ground for team 1 in the relationship.
-
C.
locationTeam2Home
Indicates that the specified location serves as the home venue or home ground for the second team involved in the context.
-
D.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
E.
ownedTeamHomeState
Indicates that the owning entity’s home or primary location is in the same state as the team’s home state.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e98cbebc8190941e76259c988790 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:53 p.m.