Triple
T2849110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Orion |
E63049
|
entity |
| Predicate | roleAtBattleOfTheNile |
P28183
|
FINISHED |
| Object | served in Nelson’s van division |
—
|
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: served in Nelson’s van division | Statement: [HMS Orion, roleAtBattleOfTheNile, served in Nelson’s van division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfTheNile Context triple: [HMS Orion, roleAtBattleOfTheNile, served in Nelson’s van division]
-
A.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
B.
joinsNile
Indicates that one river or watercourse flows into and becomes part of the Nile River.
-
C.
locatedOnBankOfNile
Indicates that something is situated on or directly adjacent to the banks of the Nile River.
-
D.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
-
E.
notableRiverCrossingRole
Indicates that an entity plays a significant role as a location or feature involved in the crossing of a river.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf41ac24819087c5b72e3b84117c |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.