Triple
T35540415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Californian |
E1027043
|
entity |
| Predicate | captainDuringTitanicDisaster |
P884
|
FINISHED |
| Object | Stanley Lord |
—
|
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: Stanley Lord | Statement: [SS Californian, captainDuringTitanicDisaster, Stanley Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainDuringTitanicDisaster Context triple: [SS Californian, captainDuringTitanicDisaster, Stanley Lord]
-
A.
captainAtTimeOfSinking
Indicates that the subject was serving as the ship’s captain at the specific time when the ship sank.
-
B.
captainInName
Indicates that an entity’s name or title explicitly includes the word “Captain.”
-
C.
crewDepicted
Indicates that a particular crew or group of crew members is visually represented or shown in some form of media or depiction.
-
D.
captain
chosen
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
E.
captainDuringExpedition
Indicates that an entity served as the captain of another entity (such as a ship, team, or mission) for the duration of a specific expedition.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:04 p.m.