Triple
T15693162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GR-43 (Thessaly) |
E380384
|
entity |
| Predicate | isSubcodeOf |
P109754
|
FINISHED |
| Object | Thessaly regional codes |
—
|
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: Thessaly regional codes | Statement: [GR-43 (Thessaly), isSubcodeOf, Thessaly regional codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubcodeOf Context triple: [GR-43 (Thessaly), isSubcodeOf, Thessaly regional codes]
-
A.
isSubsegmentOf
Indicates that one segment is entirely contained within and forms a continuous part of another, larger segment.
-
B.
isSubnetworkOf
Indicates that one network is a contained, subordinate, or component part of another, larger network.
-
C.
subsumedBy
chosen
Indicates that one entity is more specific and fully contained within another, more general entity in a hierarchical or set-inclusion sense.
-
D.
isSubstageOf
Indicates that one stage or phase is a component or smaller part within a larger, encompassing stage or phase.
-
E.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.