Triple
T35757089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | combined services expedition |
E1033470
|
entity |
| Predicate | typicallyOperatesIn |
P26656
|
FINISHED |
| Object | remote regions |
—
|
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: remote regions | Statement: [combined services expedition, typicallyOperatesIn, remote regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyOperatesIn Context triple: [combined services expedition, typicallyOperatesIn, remote regions]
-
A.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
B.
alsoOperatesIn
chosen
Indicates that an entity, in addition to its primary location or domain, conducts operations or activities in another specified place or context.
-
C.
operatesPrimarilyOn
Indicates that one entity is mainly or chiefly used to act upon, affect, or process another entity.
-
D.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
E.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.