Triple
T2584092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Gold Coast |
E57157
|
entity |
| Predicate | significantMovement |
P259
|
FINISHED |
| Object | Gold Coast independence movement |
—
|
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: Gold Coast independence movement | Statement: [British Gold Coast, significantMovement, Gold Coast independence movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantMovement Context triple: [British Gold Coast, significantMovement, Gold Coast independence movement]
-
A.
significantEvent
chosen
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
significantRevisionIn
Indicates that one entity represents a substantial or important change made within another entity, such as a major update or revision occurring in a larger work or version.
-
C.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
D.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
E.
recordsMovementOf
Indicates that something captures or logs the movement or change in position of an entity over time.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cb33a08190a3eae1a95e1b63bf |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.