Triple
T6249503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arima |
E140010
|
entity |
| Predicate | grantedBoroughStatusBy |
P32451
|
FINISHED |
| Object | British colonial authorities |
—
|
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: British colonial authorities | Statement: [Arima, grantedBoroughStatusBy, British colonial authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedBoroughStatusBy Context triple: [Arima, grantedBoroughStatusBy, British colonial authorities]
-
A.
hadBoroughStatus
Indicates that an entity previously possessed the official status or designation of a borough.
-
B.
hadBoroughStatusFrom
Indicates that an entity held the legal or administrative status of a borough starting from a specified point in time.
-
C.
cityStatusGrantedBy
Indicates that one entity (such as a person, authority, or institution) formally granted or conferred city status upon another entity (typically a settlement or locality).
-
D.
grantedStatus
chosen
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
E.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633c5f2081909b0246e061f8a7d9 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.