Triple
T8048547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azadi Stadium |
E187614
|
entity |
| Predicate | hasScoreRecord |
P80730
|
FINISHED |
| Object | attendance often exceeding 100000 in past decades |
—
|
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: attendance often exceeding 100000 in past decades | Statement: [Azadi Stadium, hasScoreRecord, attendance often exceeding 100000 in past decades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreRecord Context triple: [Azadi Stadium, hasScoreRecord, attendance often exceeding 100000 in past decades]
-
A.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
-
B.
scoringRecord
Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
-
C.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
-
D.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
E.
hasScoreboard
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7711f48190af2002533c2e426a |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:24 p.m.