Triple
T786989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semper Occultus |
E16824
|
entity |
| Predicate | officialStatusWithOSS |
P3927
|
FINISHED |
| Object | unofficial |
—
|
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: unofficial | Statement: [Semper Occultus, officialStatusWithOSS, unofficial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialStatusWithOSS Context triple: [Semper Occultus, officialStatusWithOSS, unofficial]
-
A.
coOfficialStatusIn
Indicates that two or more entities share the same official status within a specified context, such as a jurisdiction, organization, or system.
-
B.
canonicalStatus
chosen
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
C.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
D.
OSIApproved
Indicates that a software license has been reviewed and approved by the Open Source Initiative (OSI) as complying with its Open Source Definition.
-
E.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a78171908190a38a70274bfbebf9 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.