Triple
T30605761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto Corsa |
E779037
|
entity |
| Predicate | hasInUniverseGovernmentType |
P130835
|
FINISHED |
| Object | municipality |
—
|
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: municipality | Statement: [Porto Corsa, hasInUniverseGovernmentType, municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseGovernmentType Context triple: [Porto Corsa, hasInUniverseGovernmentType, municipality]
-
A.
hasGovernmentTypeCountry
Indicates that a country possesses or is characterized by a particular form or type of government.
-
B.
inUniverseGoverningBody
Indicates that a governing body exists and operates within the context or setting of a particular fictional or defined universe.
-
C.
hasGovernmentalBodyType
chosen
Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
-
D.
governmentTypeSupported
Indicates that an entity endorses, backs, or is in favor of a particular form or system of government.
-
E.
hasFormOfGovernmentContext
Indicates that an entity has a particular form of government specifically within a given contextual scope (such as a time period, jurisdiction, or situation).
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: April 29, 2026, 8:25 p.m.