Triple
T30365461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagamese |
E772407
|
entity |
| Predicate | degreeOfStandardization |
P65362
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Nagamese, degreeOfStandardization, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: degreeOfStandardization Context triple: [Nagamese, degreeOfStandardization, low]
-
A.
hasStandardizationLevel
chosen
Indicates the degree or extent to which something conforms to an established standard or set of standardized criteria.
-
B.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
C.
hasStandardizationEffort
Indicates that there is an organized effort or process to standardize something, such as practices, formats, or specifications, across relevant entities or contexts.
-
D.
componentStandardization
Indicates that one entity is standardized, normalized, or made uniform according to the specifications, rules, or format defined by another entity.
-
E.
standardizationInfluence
Indicates the extent to which one entity’s standards, norms, or standardization efforts shape, guide, or constrain another entity’s practices, processes, or specifications.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6827fabc88190a34dffaa5c83e1f1 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:58 p.m.