Triple
T10785526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suez Canal pilots |
E254441
|
entity |
| Predicate | boardsFrom |
P54736
|
FINISHED |
| Object | pilot boat |
—
|
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: pilot boat | Statement: [Suez Canal pilots, boardsFrom, pilot boat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardsFrom Context triple: [Suez Canal pilots, boardsFrom, pilot boat]
-
A.
homeBoard
Indicates that an entity serves as the primary or home board associated with another entity (such as a user, project, or collection).
-
B.
board
chosen
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
C.
boardedBy
Indicates that an entity (such as a vehicle, vessel, or structure) is entered or mounted by another entity (such as a person or group), typically for travel, inspection, or occupation.
-
D.
hasBoardComposition
Indicates that an entity has a specific structure or makeup of its governing board, such as the types or proportions of members who serve on it.
-
E.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d44b488190a9f3ab9b177e737a |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.