Triple
T8463602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balcarce 50 |
E200102
|
entity |
| Predicate | isCommonMetonymFor |
P71235
|
FINISHED |
| Object | Argentine presidency |
—
|
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: Argentine presidency | Statement: [Balcarce 50, isCommonMetonymFor, Argentine presidency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonMetonymFor Context triple: [Balcarce 50, isCommonMetonymFor, Argentine presidency]
-
A.
hasMetaphoricalForm
Indicates that one entity is expressed, represented, or understood through a metaphorical form or figurative expression involving another entity.
-
B.
oftenUsedAsNameFor
chosen
Indicates that something frequently serves as a name or designation for another entity.
-
C.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
D.
isCommonAbbreviation
Indicates that one term is a widely used shortened or abbreviated form of another term.
-
E.
isCommonlyDefinedBy
Indicates that something is typically or most frequently characterized, specified, or described by a particular definition, property, or set of criteria.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a39bd48190b72be7e03cff323b |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.