Triple
T23361470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogasawara Maru ferry |
E593194
|
entity |
| Predicate | cannotCarry |
P61996
|
FINISHED |
| Object | private cars over long distance road-style ferry service |
—
|
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: private cars over long distance road-style ferry service | Statement: [Ogasawara Maru ferry, cannotCarry, private cars over long distance road-style ferry service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotCarry Context triple: [Ogasawara Maru ferry, cannotCarry, private cars over long distance road-style ferry service]
-
A.
cannotBeHeldBy
chosen
Indicates that one entity is not allowed or not able to possess, carry, or be in control of another entity.
-
B.
canBeBorneBy
Indicates that one entity is capable of being carried, supported, or transported by another entity.
-
C.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
D.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
E.
canBring
Indicates that one entity has the ability or permission to bring another entity or item to a particular place or context.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0a8669c819098b88ae6712e3f88 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:30 p.m.