Triple
T38373090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Vaquerito |
E893543
|
entity |
| Predicate | usedNomDeGuerre |
P39531
|
FINISHED |
| Object | El Vaquerito |
—
|
NE NERFINISHED |
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: El Vaquerito | Statement: [El Vaquerito, usedNomDeGuerre, El Vaquerito]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedNomDeGuerre Context triple: [El Vaquerito, usedNomDeGuerre, El Vaquerito]
-
A.
nomDeGuerre
chosen
Indicates that an entity uses or is known by a pseudonymous or war-related alias instead of their real name.
-
B.
notableCommanderNickname
Indicates that a notable military commander is commonly known by a particular nickname.
-
C.
nicknamedByAllies
Indicates that an entity is referred to by a particular nickname specifically given or used by its allies.
-
D.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
E.
hasNotableWeaponNamedAfter
Indicates that an entity possesses a notable weapon that is named after another specific 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.