Triple
T28840578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lidcombe |
E728303
|
entity |
| Predicate | industrialFeature |
P135406
|
FINISHED |
| Object | warehouses |
—
|
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: warehouses | Statement: [Lidcombe, industrialFeature, warehouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialFeature Context triple: [Lidcombe, industrialFeature, warehouses]
-
A.
industrialFocus
Indicates a relationship where an entity is primarily concerned with, specialized in, or directed toward a particular industrial sector or area of industrial activity.
-
B.
industrialCategory
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
-
C.
industrialTheme
Indicates that something is characterized by or associated with an industrial style, atmosphere, or subject matter.
-
D.
industrialStructure
chosen
Indicates a structural or organizational relationship involving industrial facilities, systems, or frameworks.
-
E.
industrializes
Indicates the process by which an entity transforms its economy or operations from primarily agrarian or manual production to large-scale, mechanized, and industrial production.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:40 a.m.