Triple
T13101232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base Realignment and Closure |
E310721
|
entity |
| Predicate | notableRound |
P108064
|
FINISHED |
| Object | 1991 BRAC round |
—
|
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: 1991 BRAC round | Statement: [Base Realignment and Closure, notableRound, 1991 BRAC round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRound Context triple: [Base Realignment and Closure, notableRound, 1991 BRAC round]
-
A.
notableGameRound
Indicates that a particular game round is especially significant or noteworthy within the context of the game or competition.
-
B.
notableTournament
Indicates that an entity is a tournament of particular significance or prominence in relation to another entity.
-
C.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
D.
notablePlay
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
E.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981515d488190908d3cca1b84a42d |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:04 p.m.