Triple
T20967546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAU |
E516408
|
entity |
| Predicate | typicallyCorrespondsTo |
P83591
|
FINISHED |
| Object | municipalities |
—
|
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: municipalities | Statement: [LAU, typicallyCorrespondsTo, municipalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyCorrespondsTo Context triple: [LAU, typicallyCorrespondsTo, municipalities]
-
A.
correspondsWith
Indicates that two entities are in mutual alignment or agreement, such that one matches, parallels, or is equivalent to the other in a specified respect.
-
B.
relatedCorrespondence
Indicates that there exists a piece of correspondence (such as a letter, email, or message) that is associated with or pertains to the related entity.
-
C.
partiallyCorrespondsTo
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
-
D.
compactCaseCorrespondsTo
Indicates that a compact or abbreviated form of a case corresponds to, or is equivalent to, a fuller or standard representation of that case.
-
E.
oftenRefersTo
chosen
Indicates that one entity is frequently used to mention, denote, or reference another entity in common usage or context.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb9d6b548190af7214ad2468cfbf |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:37 p.m.