Triple
T5481235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA1 |
E123469
|
entity |
| Predicate | standardizationArea |
P19702
|
FINISHED |
| Object | mobile services |
—
|
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: mobile services | Statement: [SA1, standardizationArea, mobile services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizationArea Context triple: [SA1, standardizationArea, mobile services]
-
A.
standardizationScope
chosen
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
-
B.
countryOfStandardization
Indicates that a given standard, specification, or norm is officially established, adopted, or primarily recognized within a particular country.
-
C.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
D.
standardArea
Indicates that an entity has a designated or officially defined area or size that serves as a standard reference.
-
E.
regionStandard
Indicates that something conforms to, is defined by, or is governed according to the official standards or norms of a particular region.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.