Triple
T26776477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentine national anthem |
E670131
|
entity |
| Predicate | currentOfficialVersion |
P13927
|
FINISHED |
| Object | abridged text |
—
|
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: abridged text | Statement: [Argentine national anthem, currentOfficialVersion, abridged text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOfficialVersion Context triple: [Argentine national anthem, currentOfficialVersion, abridged text]
-
A.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
B.
liveVersionType
Indicates the type or category of a version that is currently live or active.
-
C.
latestMajorVersionNumber
Indicates the relationship that specifies the most recent major version number associated with an entity.
-
D.
currentVersionAdopted
chosen
Indicates that a specified version is the one presently in use or officially adopted by the relevant entity or system.
-
E.
latestCoreVersion
Indicates that one entity specifies or identifies the most recent or up-to-date core version associated with another 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 27, 2026, 4:05 a.m.