Triple
T21522606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rel-18 |
E531011
|
entity |
| Predicate | includesFeatureArea |
P6142
|
FINISHED |
| Object | enhanced MIMO |
—
|
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: enhanced MIMO | Statement: [Rel-18, includesFeatureArea, enhanced MIMO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFeatureArea Context triple: [Rel-18, includesFeatureArea, enhanced MIMO]
-
A.
includesCapabilityArea
Indicates that one entity encompasses or contains a specific capability area as part of its overall scope or functionality.
-
B.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
C.
containsThemeArea
chosen
Indicates that one entity includes or encompasses a specific thematic area as part of its scope or content.
-
D.
includesFeatureTypes
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
E.
includesAreaType
Indicates that one entity encompasses or contains another entity of a specified area type within its scope or boundaries.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884db3ac81909e77d22d607ac72d |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.