Triple
T22591860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orkut |
E564968
|
entity |
| Predicate | hadSecurityIssues |
P3249
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Orkut, hadSecurityIssues, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSecurityIssues Context triple: [Orkut, hadSecurityIssues, yes]
-
A.
hadIssue
Indicates that an entity experienced, encountered, or was affected by a particular problem, defect, or difficulty.
-
B.
hadMultipleIssues
Indicates that the subject experienced more than one problem, error, or issue in the relevant context.
-
C.
majorSecurityIssue
chosen
Indicates that the subject faces or causes a significant security vulnerability or threat.
-
D.
hasSecurityConsideration
Indicates that there is a relevant security-related issue, risk, or precaution associated with the referenced entity.
-
E.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
- F. None of above.
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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f16162c2cc8190a506776ac52356d7 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:49 p.m.