Triple
T12479433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelson captured San José by boarding from San Nicolás |
E298264
|
entity |
| Predicate | ledByRank |
P105228
|
FINISHED |
| Object | Rear Admiral |
—
|
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: Rear Admiral | Statement: [Nelson captured San José by boarding from San Nicolás, ledByRank, Rear Admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledByRank Context triple: [Nelson captured San José by boarding from San Nicolás, ledByRank, Rear Admiral]
-
A.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
B.
namedForRank
Indicates that something is named after a specific rank or title held by an entity.
-
C.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
- F. None of above. chosen
Provenance (4 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e5f8d04819086d1ad4d62364005 |
completed | April 10, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:56 p.m.