Triple
T2556395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Developer Edition |
E56738
|
entity |
| Predicate | featureSet |
P40827
|
FINISHED |
| Object | full-featured |
—
|
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: full-featured | Statement: [Developer Edition, featureSet, full-featured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureSet Context triple: [Developer Edition, featureSet, full-featured]
-
A.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
B.
featuresGroup
Indicates that an entity includes or is associated with a specific group as one of its features or components.
-
C.
featuresFormat
Indicates that something (such as a product, service, or medium) is presented, delivered, or made available in a particular format or configuration.
-
D.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
-
E.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd5a1cd508190a660b9a3c6b7cbcb |
completed | March 7, 2026, 7:37 a.m. |
Created at: March 6, 2026, 9:48 p.m.