Triple
T13693819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy leadership under Nelson |
E328334
|
entity |
| Predicate | hadFlagCaptain |
P42935
|
FINISHED |
| Object | Thomas Hardy at Trafalgar |
—
|
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: Thomas Hardy at Trafalgar | Statement: [Royal Navy leadership under Nelson, hadFlagCaptain, Thomas Hardy at Trafalgar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFlagCaptain Context triple: [Royal Navy leadership under Nelson, hadFlagCaptain, Thomas Hardy at Trafalgar]
-
A.
hadOwnFlag
Indicates that an entity possessed and used its own distinct flag as a symbol of identification or authority.
-
B.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
C.
hasNotableCaptain
chosen
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
D.
losingCaptain
Indicates that the referenced captain is the one who lost in a particular contest, game, or competitive event.
-
E.
hasFlagstaff
Indicates that one entity possesses, contains, or is equipped with a flagstaff (a pole or staff for displaying a flag).
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8757b648190a26181efbad09a43 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.