Triple
T3346052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algeciras–Tangier Med |
E70376
|
entity |
| Predicate | operatesAcross |
P28884
|
FINISHED |
| Object | international border |
—
|
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: international border | Statement: [Algeciras–Tangier Med, operatesAcross, international border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAcross Context triple: [Algeciras–Tangier Med, operatesAcross, international border]
-
A.
operatesInCountries
Indicates that an entity conducts its activities or business within the specified countries.
-
B.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
C.
operatesInternationally
chosen
Indicates that the entity conducts activities or business across national borders in multiple countries.
-
D.
alsoOperatesIn
Indicates that an entity, in addition to its primary location or domain, conducts operations or activities in another specified place or context.
-
E.
operatesToContinents
Indicates that an entity conducts or provides operations or services that extend across or are directed toward multiple continents.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f4ff888190bf14b9b7fbe9bcee |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.