Triple
T7808012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Argentina |
E180603
|
entity |
| Predicate | currentTextBasedOn |
P4593
|
FINISHED |
| Object | 1994 constitutional reform |
—
|
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: 1994 constitutional reform | Statement: [Constitution of Argentina, currentTextBasedOn, 1994 constitutional reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentTextBasedOn Context triple: [Constitution of Argentina, currentTextBasedOn, 1994 constitutional reform]
-
A.
currentText
Indicates that the referenced text is the one presently in effect, use, or display, as opposed to past or alternative versions.
-
B.
basedOnText
chosen
Indicates that something is derived, adapted, or developed from a specific text source.
-
C.
textContent
Indicates that one entity is the textual content or written material contained within another entity.
-
D.
centralText
Indicates that one text element is positioned or designated as the central or primary text relative to surrounding content or layout.
-
E.
textBy
Indicates that a given text or written content was authored or produced by 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:36 p.m.