Triple
T35540384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Carpathia |
E1027042
|
entity |
| Predicate | crewHonored |
P183223
|
FINISHED |
| Object | Captain Arthur Rostron |
—
|
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: Captain Arthur Rostron | Statement: [RMS Carpathia, crewHonored, Captain Arthur Rostron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewHonored Context triple: [RMS Carpathia, crewHonored, Captain Arthur Rostron]
-
A.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
-
B.
campaignHonours
Indicates that an entity has received formal recognition or awards for its participation in a specific campaign.
-
C.
honoredAlongside
Indicates that two or more entities are recognized or celebrated together in the same honor, award, or commemorative context.
-
D.
medalOfHonorFor
Indicates that one entity is awarded or associated with a Medal of Honor in recognition of actions or service performed by another entity.
-
E.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.