Triple
T13374245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INBA |
E319141
|
entity |
| Predicate | abbrLanguage |
P88970
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [INBA, abbrLanguage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbrLanguage Context triple: [INBA, abbrLanguage, Spanish]
-
A.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
B.
commonAbbreviationLanguage
Indicates that one language is commonly abbreviated or represented by another language or code in written or symbolic form.
-
C.
hasAcronymExpansionLanguage
Indicates that a specified language is the language in which an acronym’s full expansion is expressed.
-
D.
shortFormLanguage
chosen
Indicates that one entity is a shortened or abbreviated language representation or code corresponding to another language entity.
-
E.
suffixLanguage
Indicates that one language is used as a suffix or ending element in the formation or representation of another language or linguistic expression.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcda64a48190b53243a763cd175b |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.