Triple
T3831990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L200 |
E91033
|
entity |
| Predicate | hasFeatureLevel |
P2393
|
FINISHED |
| Object | mid-range equipment |
—
|
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: mid-range equipment | Statement: [L200, hasFeatureLevel, mid-range equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeatureLevel Context triple: [L200, hasFeatureLevel, mid-range equipment]
-
A.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
C.
hasLevel
chosen
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
D.
featureLevelComparedTo
Indicates a comparative relationship between entities based on their feature level, specifying how one entity’s feature level ranks relative to another’s.
-
E.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8787bc8190819a7af975b609df |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.