Triple
T16552470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NUTS |
E402104
|
entity |
| Predicate | relationToLAU |
P124033
|
FINISHED |
| Object | LAU lies below NUTS 3 level |
—
|
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: LAU lies below NUTS 3 level | Statement: [NUTS, relationToLAU, LAU lies below NUTS 3 level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToLAU Context triple: [NUTS, relationToLAU, LAU lies below NUTS 3 level]
-
A.
relationToMLS
Indicates a relationship or association that an entity has with a specific MLS (Multiple Listing Service) system or record.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
-
D.
addressesRelationship
Indicates that one entity directs communication, remarks, or attention specifically toward another entity.
-
E.
landRelation
Indicates a spatial or ownership-based relationship between entities and a specific piece or area of land.
- F. None of above. chosen
Provenance (4 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc6735481908b59bbf80fb3469b |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.