Triple
T34332958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fatima |
E881066
|
entity |
| Predicate | hasMaritimeSetting |
P44766
|
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: [Fatima, hasMaritimeSetting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeSetting Context triple: [Fatima, hasMaritimeSetting, true]
-
A.
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.
-
B.
maritimeSettingFor
chosen
Indicates that one entity serves as the maritime or ocean-related environment or backdrop in which another entity is situated or occurs.
-
C.
hasMaritimeZone
Indicates that one entity possesses or is associated with a specific maritime area or jurisdictional sea zone.
-
D.
isMaritimeStyle
Indicates that something exhibits characteristics or design elements associated with maritime or nautical style.
-
E.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01926e2f348190a632eff5c91db5e0 |
completed | May 11, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_6a01923488f4819094d79a27f4bc8ab8 |
completed | May 11, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:58 a.m.