Triple
T6327517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BeiDou |
E141895
|
entity |
| Predicate | globalServiceOperational |
P70864
|
FINISHED |
| Object | around 2020 |
—
|
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: around 2020 | Statement: [BeiDou, globalServiceOperational, around 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalServiceOperational Context triple: [BeiDou, globalServiceOperational, around 2020]
-
A.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
-
B.
typicalOperatorService
Indicates that an entity commonly performs or provides a particular operational service in a standard or expected manner.
-
C.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
D.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
E.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
- F. None of above. chosen
Provenance (4 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e9532081908277f10ec380a486 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:29 p.m.