Triple
T36147879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grey Seas of Jutland |
E1045502
|
entity |
| Predicate | titleCharacterOrSubject |
P200695
|
FINISHED |
| Object | Battle of Jutland |
—
|
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: Battle of Jutland | Statement: [The Grey Seas of Jutland, titleCharacterOrSubject, Battle of Jutland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCharacterOrSubject Context triple: [The Grey Seas of Jutland, titleCharacterOrSubject, Battle of Jutland]
-
A.
characterTitle
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
B.
titleCharacterString
Indicates that one entity is the textual string representing the title associated with another entity.
-
C.
titleSubjectName
Indicates that the predicate specifies the name of the subject associated with a given title.
-
D.
titularCharacterOf
Indicates that one entity is the main or title character featured in the work represented by the other entity.
-
E.
titleCharacterNamedAfter
Indicates that a work’s title character is named after, or shares their name with, another specific entity.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
| PDg | Predicate description generation | batch_69ffa15c3f348190a59403bc72ac9ed4 |
completed | May 9, 2026, 9:04 p.m. |
Created at: May 3, 2026, 4:08 p.m.