Triple
T16040599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Personal Software Process |
E389082
|
entity |
| Predicate | component |
P35
|
FINISHED |
| Object | PSP2.1 |
E1190741
|
NE 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: PSP2.1 | Statement: [Personal Software Process, component, PSP2.1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PSP2.1 Context triple: [Personal Software Process, component, PSP2.1]
-
A.
PSP1.1
chosen
PSP1.1 is an introductory level of the Personal Software Process that guides individual developers in systematically planning, measuring, and improving their software development work.
-
B.
PSP
PSP is an alternative name for Public School English, referring to the English language curriculum or program used in public schools.
-
C.
PSP
PSP is the IATA airport code for Palm Springs International Airport, which serves the Palm Springs area in Southern California.
-
D.
PSP
The PSP was a Dutch political party that combined socialist principles with a strong commitment to pacifism and anti-militarism.
-
E.
PSP
PSP is the acronym commonly used for the Public Security Police, a national law enforcement body responsible for maintaining public order and safety.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e18340686881909135fc43a0a71b20 |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffe474f89c819086db832b793c15ed |
completed | May 10, 2026, 1:50 a.m. |
Created at: April 10, 2026, 4:56 a.m.