Triple
T34441860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EASA CS-VLA |
E884117
|
entity |
| Predicate | categoryLimit |
P91382
|
FINISHED |
| Object | single-engine aeroplanes |
—
|
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: single-engine aeroplanes | Statement: [EASA CS-VLA, categoryLimit, single-engine aeroplanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryLimit Context triple: [EASA CS-VLA, categoryLimit, single-engine aeroplanes]
-
A.
hasCategoryLengthRestriction
Indicates that there is a constraint on the allowable length of a category, such as its name, identifier, or structural size.
-
B.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
C.
definesLimitOf
chosen
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2 a.m.