Triple
T6310212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambridge |
E141478
|
entity |
| Predicate | isIndustrialCommunity |
P69984
|
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: [Ambridge, isIndustrialCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndustrialCommunity Context triple: [Ambridge, isIndustrialCommunity, true]
-
A.
isIndustrialAreaOf
Indicates that a location functions primarily as an industrial zone or district associated with a specified area or jurisdiction.
-
B.
isIndustrialCenter
Indicates that a place functions as a major hub of industrial activity, production, or manufacturing within a region.
-
C.
isIndustrialRegion
Indicates that a given area functions primarily as a center of industrial activity, characterized by significant manufacturing, production, or related industrial operations.
-
D.
hasIndustrialTown
Indicates that an entity possesses or is associated with a town characterized primarily by industrial activities or facilities.
-
E.
hasIndustrialAreaType
Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0648074b081908ba661651ba705a7 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:28 p.m.