Triple
T357138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magellan–Elcano expedition |
E7568
|
entity |
| Predicate | fleetSizeAtDeparture |
P1848
|
FINISHED |
| Object | 5 ships |
—
|
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: 5 ships | Statement: [Magellan–Elcano expedition, fleetSizeAtDeparture, 5 ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetSizeAtDeparture Context triple: [Magellan–Elcano expedition, fleetSizeAtDeparture, 5 ships]
-
A.
fleetSize
chosen
Indicates the total number of vehicles, vessels, or units that collectively make up a fleet associated with an entity.
-
B.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
C.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
D.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event or situation.
-
E.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebaf0c9881909313f98818e7fa58 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e959ce948190a201c017eecb7c95 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.