Triple
T14569368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindenburg disaster |
E341868
|
entity |
| Predicate | approachPhase |
P40614
|
FINISHED |
| Object | mooring |
—
|
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: mooring | Statement: [Hindenburg disaster, approachPhase, mooring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachPhase Context triple: [Hindenburg disaster, approachPhase, mooring]
-
A.
applicationPhase
Indicates the specific stage or step an application is currently in within a broader application process.
-
B.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
C.
engagementPhase
Indicates the specific stage or phase an ongoing interaction, project, or relationship is currently in within its overall lifecycle.
-
D.
acquisitionPhase
Indicates the stage or phase within an overall acquisition process in which the related entities are currently involved.
-
E.
movementPhase
chosen
Indicates the specific stage or step within a larger movement or motion process that an action or entity is currently in.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f2121481908f2385637944785d |
completed | April 14, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.