Triple
T1008991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PeopleSoft |
E21777
|
entity |
| Predicate | acquisitionStatus |
P23562
|
FINISHED |
| Object | completed |
—
|
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: completed | Statement: [PeopleSoft, acquisitionStatus, completed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionStatus Context triple: [PeopleSoft, acquisitionStatus, completed]
-
A.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
B.
seeksStatusAs
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
-
C.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
D.
initiationStatus
Indicates the current state or phase of beginning or starting a process, activity, or relationship between entities.
-
E.
catalogueStatus
Indicates the current state or condition of an item within a catalogue or listing system (e.g., active, inactive, pending).
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7f2d1b081908eb2df54e91c8c1d |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:41 p.m.