Triple
T16363730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XO |
E397379
|
entity |
| Predicate | confidentialityStatusDuringUse |
P94707
|
FINISHED |
| Object | internal-only |
—
|
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: internal-only | Statement: [XO, confidentialityStatusDuringUse, internal-only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confidentialityStatusDuringUse Context triple: [XO, confidentialityStatusDuringUse, internal-only]
-
A.
confidentialityStatusAtTheTime
chosen
Indicates the level or state of confidentiality that applied to something at a specific point in time.
-
B.
usesModeForConfidentiality
Indicates that an entity employs a particular mode, method, or mechanism specifically to ensure or enhance the confidentiality of information.
-
C.
confidentialityProtectedBy
Indicates that the confidentiality of some information is safeguarded or ensured by a specified protection mechanism, policy, or entity.
-
D.
hasConfidentialityObligation
Indicates that an entity is bound by a duty to keep certain information secret and not disclose it to unauthorized parties.
-
E.
usesConfidentialProceedings
Indicates that an entity conducts or relies on proceedings that are non-public and protected by confidentiality restrictions.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3aada88190a6e01f04c494a6ac |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.