Triple
T8105130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superclásico (Boca vs River) |
E189207
|
entity |
| Predicate | policePresence |
P80479
|
FINISHED |
| Object | heavy |
—
|
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: heavy | Statement: [Superclásico (Boca vs River), policePresence, heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policePresence Context triple: [Superclásico (Boca vs River), policePresence, heavy]
-
A.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
-
B.
policeControl
Indicates that one entity exercises authoritative oversight, regulation, or enforcement power over another, as a police force does over people or areas under its jurisdiction.
-
C.
hasPoliceStationsIn
Indicates that one entity possesses, manages, or contains one or more police stations located within the area or jurisdiction of another entity.
-
D.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
E.
hasPoliceDepartment
Indicates that an entity possesses, is served by, or is administratively associated with a police department.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42c0ce6481909887be82c8019383 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:31 p.m.