Triple
T29431017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard |
E746431
|
entity |
| Predicate | hasRelationshipTypeWithMarina |
P201421
|
FINISHED |
| Object | romantic relationship |
—
|
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: romantic relationship | Statement: [Howard, hasRelationshipTypeWithMarina, romantic relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipTypeWithMarina Context triple: [Howard, hasRelationshipTypeWithMarina, romantic relationship]
-
A.
hasMarinaStatus
Indicates that an entity has a specific status or classification related to a marina (e.g., operational, planned, closed).
-
B.
hasMarinaService
Indicates that an entity provides marina-related services or facilities for boats and watercraft.
-
C.
marinaInstanceOf
Indicates that something is classified as an instance of the concept or type "marina."
-
D.
hasMarinaName
Indicates that an entity (such as a marina) is associated with a specific name identifying that marina.
-
E.
hasMarinaOrStaithe
Indicates that a place includes or is associated with a marina or staithe (a landing stage or mooring area for boats).
- F. None of above. chosen
Provenance (4 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fff4525ce48190b1d760539e68aadc |
completed | May 10, 2026, 2:58 a.m. |
Created at: April 28, 2026, 3:13 p.m.