Triple
T8290200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Insider |
E193873
|
entity |
| Predicate | featureStatus |
P74449
|
FINISHED |
| Object | pre-release 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: pre-release features | Statement: [Office Insider, featureStatus, pre-release features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureStatus Context triple: [Office Insider, featureStatus, pre-release features]
-
A.
featureFlag
chosen
Indicates that a particular functionality or behavior is conditionally enabled or disabled for an entity based on a configurable flag.
-
B.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
featuresService
Indicates that one entity provides, includes, or offers a particular service as a notable characteristic or component.
-
E.
implementationStatus
Indicates the current state or progress of carrying out or realizing something, such as a plan, design, or requirement.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c99fdd48190a3f304237be609a0 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.