Triple
T30705376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traiskirchen |
E781736
|
entity |
| Predicate | hasRefugeeFacilityOperator |
P39840
|
FINISHED |
| Object | Austrian Ministry of the Interior |
—
|
NE NERFINISHED |
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: Austrian Ministry of the Interior | Statement: [Traiskirchen, hasRefugeeFacilityOperator, Austrian Ministry of the Interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefugeeFacilityOperator Context triple: [Traiskirchen, hasRefugeeFacilityOperator, Austrian Ministry of the Interior]
-
A.
refugeeAdministration
chosen
Indicates the management, coordination, or oversight of services, policies, and procedures related to refugees.
-
B.
hasRefugeeCamp
Indicates that a location or entity hosts, contains, or is the site of a refugee camp.
-
C.
borderFacilityOperatedBy
Indicates that a specific border facility is managed, controlled, or run by a particular organization or authority.
-
D.
designatedAsRefuge
Indicates that an entity has been officially assigned or recognized as a refuge or place of protection.
-
E.
immigrationStationInOperationFrom
Indicates the date from which an immigration station began operating or being in active service.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00ab25c5b48190ad07ff508392ef56 |
completed | May 10, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_6a00a8a5cfc48190bbe97fb2bbd1b947 |
completed | May 10, 2026, 3:47 p.m. |
Created at: April 29, 2026, 8:35 p.m.