Triple
T8367004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Manara Square |
E197151
|
entity |
| Predicate | hasCivicUse |
P80014
|
FINISHED |
| Object | public speeches |
—
|
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: public speeches | Statement: [Al-Manara Square, hasCivicUse, public speeches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCivicUse Context triple: [Al-Manara Square, hasCivicUse, public speeches]
-
A.
hasCivicFunction
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
-
B.
hasCivicOrganization
Indicates that an entity is associated with, supported by, or contains a civic organization, such as a community, volunteer, or public-interest group.
-
C.
hasMunicipalService
Indicates that a municipality provides or is responsible for a specific public service to a given area, facility, or population.
-
D.
hasCivicAmenity
chosen
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
E.
hasCivilArea
Indicates that an administrative or political entity encompasses or is associated with a specific civil (local administrative) area.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808cf80c8190941c3cc0248a5df2 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.