Triple
T17560494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | plpython2u |
E427684
|
entity |
| Predicate | trustedStatus |
P127947
|
FINISHED |
| Object | untrusted |
—
|
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: untrusted | Statement: [plpython2u, trustedStatus, untrusted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trustedStatus Context triple: [plpython2u, trustedStatus, untrusted]
-
A.
securedStatus
Indicates that an entity’s state, access, or data has been protected or locked down to prevent unauthorized use or modification.
-
B.
hasTrust
Indicates that one entity has confidence in the reliability, integrity, or good intentions of another entity.
-
C.
trustModel
Indicates that one entity relies on or has confidence in the reliability, integrity, or performance of another entity or system.
-
D.
trustAnchoredVia
Indicates that a relationship of trust is established or justified through a specific intermediary or anchoring mechanism (such as a trusted authority, key, or certificate).
-
E.
sponsorStatus
Indicates the current state or condition of an entity’s sponsorship relationship, such as whether it is active, pending, or inactive.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.