Triple
T14802409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marulan |
E347939
|
entity |
| Predicate | hasRuralFireServiceBrigade |
P115786
|
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: [Marulan, hasRuralFireServiceBrigade, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuralFireServiceBrigade Context triple: [Marulan, hasRuralFireServiceBrigade, true]
-
A.
hasFireServicesFrom
Indicates that one entity receives fire protection or firefighting services from another entity.
-
B.
hasFireAndRescueServiceCategory
Indicates the specific fire and rescue service classification or category assigned to an entity, such as a building, facility, or site.
-
C.
hasRuralServiceTown
Indicates that a rural area or region is associated with, and typically receives services from, a specific town that functions as its service center.
-
D.
hasRuralCouncilStatus
Indicates that an entity holds the official designation or legal status of a rural council within a given administrative or governance system.
-
E.
hasFireStation
Indicates that a location or area contains or is served by a fire station.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf30d044819082ac038e06481aab |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:33 a.m.