Triple
T5405915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davao City |
E120891
|
entity |
| Predicate | hasFirecrackerBan |
P63229
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Davao City, hasFirecrackerBan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirecrackerBan Context triple: [Davao City, hasFirecrackerBan, true]
-
A.
bannedInCountry
Indicates that something is officially prohibited or not allowed within the jurisdiction of a specified country.
-
B.
hasJetBan
Indicates that an entity is subject to a prohibition or restriction on the use or operation of jet aircraft.
-
C.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
D.
hasTourismRestriction
Indicates that there is a limitation, prohibition, or special condition affecting tourism-related activities or access in relation to the referenced entity.
-
E.
wasOnceOutlawed
Indicates that an entity was previously considered illegal or banned by an authority but is no longer outlawed.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87924c588190beb4a1be27f8d11b |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd865702ec8190831bde2c2a331f28 |
completed | March 20, 2026, 5:39 p.m. |
Created at: March 20, 2026, 2:05 p.m.