Triple

T21170028
Position Surface form Disambiguated ID Type / Status
Subject PeopleSoft Component Interface E521665 entity
Predicate canBeExposedAs P143143 FINISHED
Object SOAP web service 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: SOAP web service | Statement: [PeopleSoft Component Interface, canBeExposedAs, SOAP web service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeExposedAs
Context triple: [PeopleSoft Component Interface, canBeExposedAs, SOAP web service]
  • A. exposedAs
    Indicates that one entity reveals or publicly identifies another entity as having a hidden, false, or previously concealed role, identity, or nature.
  • B. isExposed
    Indicates that an entity is subjected or open to the influence, effects, or presence of another entity or condition.
  • C. wasExposedAs
    Indicates that an entity was revealed or uncovered as having a particular hidden identity, role, or wrongdoing.
  • D. exposedThrough
    Indicates that something becomes revealed, accessible, or affected as a result of passing through or being subjected to another thing or medium.
  • E. exposesTo
    Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
  • 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_69e0b50e30748190b186824a206d39b9 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72711be9481909f16107b71d3500a completed April 21, 2026, 7:28 a.m.
PD Predicate disambiguation batch_69e5f6027c248190a170a36612bd337e completed April 20, 2026, 9:46 a.m.
PDg Predicate description generation batch_69e5f993240c8190847c0b08e65726c8 completed April 20, 2026, 10:01 a.m.
Created at: April 16, 2026, 3 p.m.