Triple
T35523528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special English |
E1026606
|
entity |
| Predicate | controlledAspect |
P4700
|
FINISHED |
| Object | vocabulary size |
—
|
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: vocabulary size | Statement: [Special English, controlledAspect, vocabulary size]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledAspect Context triple: [Special English, controlledAspect, vocabulary size]
-
A.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
B.
controlled
chosen
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
C.
coversAspect
Indicates that one entity addresses, includes, or deals with a particular aspect or facet of another entity or topic.
-
D.
protectedAspect
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or mechanism.
-
E.
validatedAspectOf
Indicates that one entity has been checked or confirmed as a correct, acceptable, or compliant aspect or component of another entity.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 3, 2026, 4:04 p.m.