Triple
T30503194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adventure Galley |
E776193
|
entity |
| Predicate | conditionAtEnd |
P71242
|
FINISHED |
| Object | leaky and unseaworthy |
—
|
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: leaky and unseaworthy | Statement: [Adventure Galley, conditionAtEnd, leaky and unseaworthy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionAtEnd Context triple: [Adventure Galley, conditionAtEnd, leaky and unseaworthy]
-
A.
conditionAfterClosure
Indicates the state or circumstances that exist after a process, event, or entity has been formally closed or concluded.
-
B.
terminalCondition
chosen
Indicates the condition or set of conditions under which a process, interaction, or state is considered complete and should terminate.
-
C.
conditionWhenFound
Indicates the state or circumstances that were present at the time the entity was first discovered or observed.
-
D.
canEndOn
Indicates that one entity is allowed or able to terminate, conclude, or finish with another specified entity or condition.
-
E.
controlledByAtEnd
Indicates that one entity has control or governing authority over another entity at the final point or conclusion of a specified process, period, or event.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687825a248190b587438a58643a32 |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:15 p.m.