Triple
T36120126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Tyrol (under Meinhardiner dynasty) |
E1044718
|
entity |
| Predicate | todayRegionIncludes |
P15803
|
FINISHED |
| Object | Austrian state of Tyrol |
—
|
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 state of Tyrol | Statement: [County of Tyrol (under Meinhardiner dynasty), todayRegionIncludes, Austrian state of Tyrol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: todayRegionIncludes Context triple: [County of Tyrol (under Meinhardiner dynasty), todayRegionIncludes, Austrian state of Tyrol]
-
A.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
B.
currentLocationRegion
chosen
Indicates the region in which an entity is presently located.
-
C.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
D.
distributionRegionsInclude
Indicates that certain geographic or market regions are encompassed within the overall distribution coverage of a product or service.
-
E.
ISORegion
Indicates a standardized geographic or administrative region as defined by an ISO (International Organization for Standardization) code.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.