Triple
T8927813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elliott Bay Marina |
E212578
|
entity |
| Predicate | hasSlipType |
P28048
|
FINISHED |
| Object | covered slips |
—
|
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: covered slips | Statement: [Elliott Bay Marina, hasSlipType, covered slips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSlipType Context triple: [Elliott Bay Marina, hasSlipType, covered slips]
-
A.
slipType
chosen
Indicates the specific category or kind of slip involved in an action or relationship between entities.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasGripType
Indicates that one entity possesses or uses a specific type or style of grip in relation to another entity or action.
-
D.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
-
E.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6672af10819084a6e50f0302f732 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.