Triple
T20439921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feldkirch |
E501355
|
entity |
| Predicate | hasMarketRight |
P39434
|
FINISHED |
| Object | medieval market town status |
—
|
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: medieval market town status | Statement: [Feldkirch, hasMarketRight, medieval market town status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketRight Context triple: [Feldkirch, hasMarketRight, medieval market town status]
-
A.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
B.
hasMarketRole
Indicates that an entity holds or performs a specific functional role within a market or marketplace context.
-
C.
hasMarketStatus
Indicates the current commercial or trading condition of an entity, such as whether it is active, suspended, listed, or delisted in a market.
-
D.
hasMarketStructure
Indicates that one entity possesses, follows, or is characterized by a particular market structure in an economic or commercial context.
-
E.
hasRightsOver
chosen
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f20fe08190b9370b523a20153d |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.