Triple
T34730309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brisbane Northside |
E1001189
|
entity |
| Predicate | hasMajorIndustrialArea |
P146344
|
FINISHED |
| Object | Pinkenba |
E1001190
|
NE 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: Pinkenba | Statement: [Brisbane Northside, hasMajorIndustrialArea, Pinkenba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorIndustrialArea Context triple: [Brisbane Northside, hasMajorIndustrialArea, Pinkenba]
-
A.
containsIndustrialAreas
chosen
Indicates that one entity includes or encompasses industrial areas within its boundaries or scope.
-
B.
hasIndustrialAreaType
Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
-
C.
hasIndustrialZoneAlong
Indicates that an industrial zone is located adjacent to or extending along the length of a specified linear feature (such as a road, river, or boundary).
-
D.
isIndustrialAreaOf
Indicates that a location functions primarily as an industrial zone or district associated with a specified area or jurisdiction.
-
E.
hasIndustrialTown
Indicates that an entity possesses or is associated with a town characterized primarily by industrial activities or facilities.
- F. None of above.
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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a01c21d8bc481909dd9f5a6b89c0a92 |
completed | May 11, 2026, 11:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375beb79148190ab3801252894d369 |
completed | June 21, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_6a01bff5d1508190895e5bd2c04932b0 |
completed | May 11, 2026, 11:39 a.m. |
Created at: May 3, 2026, 3:59 p.m.