Triple
T34976061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krakozhian |
E1008679
|
entity |
| Predicate | hasLevelOfDevelopment |
P16858
|
FINISHED |
| Object | limited vocabulary |
—
|
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: limited vocabulary | Statement: [Krakozhian, hasLevelOfDevelopment, limited vocabulary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelOfDevelopment Context triple: [Krakozhian, hasLevelOfDevelopment, limited vocabulary]
-
A.
isDevelopmentLevelFor
Indicates that one entity represents the development or maturity level assigned to, or characteristic of, another entity.
-
B.
developmentLevel
chosen
Indicates the degree or stage of progress, advancement, or maturity that something has reached in its growth or evolution.
-
C.
hasMaximumDevelopmentIn
Indicates that something reaches its highest level or intensity of development within a specified context, condition, or location.
-
D.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
E.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 3, 2026, 4:01 p.m.