Triple
T27669645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirVision revenue management suite |
E697624
|
entity |
| Predicate | supportsDecisionMakingFor |
P200642
|
FINISHED |
| Object | pricing analysts |
—
|
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: pricing analysts | Statement: [AirVision revenue management suite, supportsDecisionMakingFor, pricing analysts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDecisionMakingFor Context triple: [AirVision revenue management suite, supportsDecisionMakingFor, pricing analysts]
-
A.
supportsDecisionOf
Indicates that one entity endorses, backs, or agrees with the decision made by another entity.
-
B.
supportsDecisionAPI
Indicates that one entity provides or enables a decision-making API service for another entity.
-
C.
hasDecisionMakingPower
Indicates that one entity possesses the authority or ability to make decisions that affect another entity or a given context.
-
D.
knownForDecision
Indicates that an entity is recognized or notable specifically for making a particular decision.
-
E.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69ff9d9ba1ac8190a0cca5764bb5904d |
completed | May 9, 2026, 8:48 p.m. |
Created at: April 27, 2026, 2:40 p.m.