Triple
T23044335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ledaig 18 Year Old |
E573832
|
entity |
| Predicate | isMaritimeStyle |
P150769
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ledaig 18 Year Old, isMaritimeStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMaritimeStyle Context triple: [Ledaig 18 Year Old, isMaritimeStyle, true]
-
A.
maritimeVariant
Indicates a version or form of something that is specifically adapted for or used in maritime (sea-related) contexts.
-
B.
hasSeafrontStyle
Indicates that something possesses a design, appearance, or character specifically associated with a seafront or coastal setting.
-
C.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
-
D.
maritimeSettingFor
Indicates that one entity serves as the maritime or ocean-related environment or backdrop in which another entity is situated or occurs.
-
E.
hasMaritimeHeritage
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18517083c8190a0850da5440e0a73 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:54 p.m.