Triple
T35540626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Olympic |
E1027048
|
entity |
| Predicate | sisterShipTo |
P3142
|
FINISHED |
| Object | RMS Titanic |
—
|
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: RMS Titanic | Statement: [RMS Olympic, sisterShipTo, RMS Titanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterShipTo Context triple: [RMS Olympic, sisterShipTo, RMS Titanic]
-
A.
sisterShip
chosen
Indicates that two ships are considered counterparts or equivalents, typically of the same design, class, or series.
-
B.
shipsWith
Indicates that one entity is delivered, packaged, or provided together with another entity as part of the same shipment or bundle.
-
C.
componentShip
Indicates that one entity is a physical or logical component or part of another entity, such that the whole is composed of or depends on that component.
-
D.
relatedShipFind
Indicates that one entity discovers, identifies, or locates another entity that is connected to it through some form of relationship.
-
E.
所属艦
Indicates a relationship where something belongs to, is assigned to, or is part of a particular ship.
- 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_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.