Triple
T28468072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TBA (Trenes de Buenos Aires) |
E720353
|
entity |
| Predicate | concessionRevokedBy |
P78730
|
FINISHED |
| Object | Argentine government |
—
|
NE NERFINISHED |
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: Argentine government | Statement: [TBA (Trenes de Buenos Aires), concessionRevokedBy, Argentine government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concessionRevokedBy Context triple: [TBA (Trenes de Buenos Aires), concessionRevokedBy, Argentine government]
-
A.
concessionBy
Indicates that one party grants, yields, or makes allowances to another, often accepting a demand, point, or condition despite initial opposition or differing interests.
-
B.
concessionExpiry
Indicates that a granted concession or special permission remains valid only until a specified expiration time or date.
-
C.
renouncedBy
Indicates that an entity has been formally rejected, disowned, or given up by another entity.
-
D.
consequenceOfRevocation
Indicates that something occurs as a direct result of a prior revocation event or decision.
-
E.
revokedFrom
chosen
Indicates that a previously granted right, permission, or status has been withdrawn from a particular entity.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 2:46 a.m.