Triple

T33023179
Position Surface form Disambiguated ID Type / Status
Subject Maia E844967 entity
Predicate industrialZone P68164 FINISHED
Object Zona Industrial da Maia NE NERFINISHED

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: Zona Industrial da Maia | Statement: [Maia, industrialZone, Zona Industrial da Maia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: industrialZone
Context triple: [Maia, industrialZone, Zona Industrial da Maia]
  • A. 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).
  • B. isIndustrialAreaOf chosen
    Indicates that a location functions primarily as an industrial zone or district associated with a specified area or jurisdiction.
  • C. hasIndustrialAreaType
    Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
  • D. containsIndustrialAreas
    Indicates that one entity includes or encompasses industrial areas within its boundaries or scope.
  • E. isIndustrialRegion
    Indicates that a given area functions primarily as a center of industrial activity, characterized by significant manufacturing, production, or related industrial operations.
  • 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_69f34950749c8190ae05cd27adb16d58 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d74b20a48190900dda1014cc13a8 completed May 3, 2026, 5:04 a.m.
PD Predicate disambiguation batch_69f6d26f27dc8190ae426a3e1573933e completed May 3, 2026, 4:43 a.m.
Created at: May 1, 2026, 1:23 a.m.