Triple
T37998845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InfoPath 2013 |
E948033
|
entity |
| Predicate | partialReplacementBy |
P40785
|
FINISHED |
| Object | PowerApps |
—
|
NE NERFINISHED |
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: PowerApps | Statement: [InfoPath 2013, partialReplacementBy, PowerApps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partialReplacementBy Context triple: [InfoPath 2013, partialReplacementBy, PowerApps]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
primaryReplacementFor
Indicates that one entity serves as the main or preferred substitute or successor for another entity.
-
C.
replacedAtPar
Indicates that one entity has been replaced by another at a specific location or position within a larger structure or sequence.
-
D.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
E.
partlyReplacedBy
chosen
Indicates that one entity has been superseded or substituted in part, but not entirely, by another entity.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:20 p.m.