Triple
T37774414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipal council of Ribemont |
E941644
|
entity |
| Predicate | hasAuthorityInArea |
P156935
|
FINISHED |
| Object | local taxation within Ribemont |
—
|
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: local taxation within Ribemont | Statement: [municipal council of Ribemont, hasAuthorityInArea, local taxation within Ribemont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorityInArea Context triple: [municipal council of Ribemont, hasAuthorityInArea, local taxation within Ribemont]
-
A.
hasRoleArea
Indicates that an entity holds or is associated with a specific functional role within a defined area or domain.
-
B.
hasProtectedAreaAuthority
Indicates that an entity holds official authority or responsibility for managing or overseeing a protected area.
-
C.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
-
D.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
E.
hasEnforcementArea
chosen
Indicates that an entity is subject to or associated with a specific geographic or jurisdictional area where certain rules, regulations, or enforcement actions apply.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.