Triple
T1369282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbados Judicial Committee (historical) |
E30073
|
entity |
| Predicate | hearsFrom |
P27001
|
FINISHED |
| Object | Barbados colonial courts |
—
|
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: Barbados colonial courts | Statement: [Barbados Judicial Committee (historical), hearsFrom, Barbados colonial courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearsFrom Context triple: [Barbados Judicial Committee (historical), hearsFrom, Barbados colonial courts]
-
A.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
B.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
C.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
-
D.
heard
Indicates that one entity perceived a sound produced by another entity or source through hearing.
-
E.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d60fdc8190a9954b74ca2b2541 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfc2134c81909cbaaa151d96e9a8 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:57 p.m.