Triple
T23001508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icon Tech |
E572643
|
entity |
| Predicate | addsOverBase |
P150602
|
FINISHED |
| Object | enhanced technology features |
—
|
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 technology features | Statement: [Icon Tech, addsOverBase, enhanced technology features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsOverBase Context triple: [Icon Tech, addsOverBase, enhanced technology features]
-
A.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
B.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
-
C.
extendsUnder
Indicates that one entity physically stretches or reaches out beneath another entity, occupying a lower position while continuing under its span or area.
-
D.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
E.
overlays
Indicates that one entity is placed on top of or superimposed over another, partially or completely covering it in the same spatial area.
- F. None of above. chosen
Provenance (4 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18353d05481909abacb48a14ef21e |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:50 p.m.