Triple
T13776059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afro-Anguillans |
E331008
|
entity |
| Predicate | historicallyEmployedIn |
P17879
|
FINISHED |
| Object | plantation agriculture |
—
|
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: plantation agriculture | Statement: [Afro-Anguillans, historicallyEmployedIn, plantation agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyEmployedIn Context triple: [Afro-Anguillans, historicallyEmployedIn, plantation agriculture]
-
A.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
B.
hasPastOccupation
Indicates that an entity previously held a particular job, role, or occupation in the past.
-
C.
workedPrimarilyOn
Indicates that an entity devoted the majority of its work, effort, or activity to a particular project, field, or subject.
-
D.
hasWorkedIn
chosen
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
E.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0238bdbc8190a946e6e5431632a5 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.