Triple
T315107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT App Inventor |
E7687
|
entity |
| Predicate | hasComponentType |
P6678
|
FINISHED |
| Object | User Interface components |
—
|
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: User Interface components | Statement: [MIT App Inventor, hasComponentType, User Interface components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentType Context triple: [MIT App Inventor, hasComponentType, User Interface components]
-
A.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
B.
componentType
chosen
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
C.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
-
D.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
E.
hasModelType
Indicates that an entity is associated with or classified under a specific model type.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea62f830819089e94b3aa3e4e187 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.