Triple
T18916707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guerra del Asiento de Negros |
E462742
|
entity |
| Predicate | tambiénConocidaComo |
P39
|
FINISHED |
| Object | Guerra del Asiento |
—
|
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: Guerra del Asiento | Statement: [Guerra del Asiento de Negros, tambiénConocidaComo, Guerra del Asiento]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tambiénConocidaComo Context triple: [Guerra del Asiento de Negros, tambiénConocidaComo, Guerra del Asiento]
-
A.
alsoKnownAs
chosen
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
B.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
C.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
D.
knownAsOneOf
Indicates that an entity is recognized or referred to as one member of a specified set of alternative names, labels, or identities.
-
E.
alsoKnownThrough
Indicates that an entity is recognized or identified by means of another entity, such as a source, context, or intermediary, through which its alternative name or identity is known.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.