Triple
T25968025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | جزيرة بريم |
E645727
|
entity |
| Predicate | كانت_موضع |
P87890
|
FINISHED |
| Object | تنافس استعماري تاريخي |
—
|
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: تنافس استعماري تاريخي | Statement: [جزيرة بريم, كانت_موضع, تنافس استعماري تاريخي]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: كانت_موضع Context triple: [جزيرة بريم, كانت_موضع, تنافس استعماري تاريخي]
-
A.
جایگاه
Indicates a positional or hierarchical relationship specifying the place, rank, or status of one entity relative to others.
-
B.
capturedPlace
Indicates that an agent took control of or seized a specific place, typically through force or strategic action.
-
C.
believedToBeSiteOf
chosen
Indicates that something is thought or assumed, though not definitively proven, to be the location where a particular event, structure, or phenomenon occurred or existed.
-
D.
wasCitadelOf
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
-
E.
المنشأ
Indicates the origin or source from which an entity, action, or relationship arises or is derived.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604cc423081908edb1fcf694f06fc |
completed | May 2, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:50 a.m.