Triple
T32523102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DGM |
E831233
|
entity |
| Predicate | internalUsage |
P47860
|
FINISHED |
| Object | internal Belgian administration |
—
|
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 Belgian administration | Statement: [DGM, internalUsage, internal Belgian administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalUsage Context triple: [DGM, internalUsage, internal Belgian administration]
-
A.
usedInternally
chosen
Indicates that something is utilized within an organization, system, or component itself rather than being exposed or provided for external use.
-
B.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
C.
usedToIntern
Indicates that one entity previously held an internship position with another entity.
-
D.
updatesUsageOf
Indicates that one entity modifies or refreshes the recorded usage state or usage data of another entity.
-
E.
isInternal
Indicates that something exists or occurs within the boundaries, structure, or inner context of a specified entity or system, rather than being external to it.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 1, 2026, 1:01 a.m.