Triple
T37029091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington plantation |
E916437
|
entity |
| Predicate | nowManagedBy |
P186925
|
FINISHED |
| Object | STINAPA Bonaire |
—
|
NE NERFINISHED |
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: STINAPA Bonaire | Statement: [Washington plantation, nowManagedBy, STINAPA Bonaire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nowManagedBy Context triple: [Washington plantation, nowManagedBy, STINAPA Bonaire]
-
A.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
-
B.
notManagedBy
Indicates that an entity is explicitly not under the control, supervision, or administrative responsibility of the specified manager or managing entity.
-
C.
isOftenManagedBy
Indicates that an entity is frequently or typically overseen, directed, or administered by another entity.
-
D.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
E.
isManagedThrough
Indicates that one entity is administered, controlled, or operated by means of another entity, typically specifying the mechanism, channel, or system used for its management.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.