Triple

T1159629
Position Surface form Disambiguated ID Type / Status
Subject Manufacturing Belt E24463 entity
Predicate laborCharacteristic P662 FINISHED
Object strong labor unions 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: strong labor unions | Statement: [Manufacturing Belt, laborCharacteristic, strong labor unions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: laborCharacteristic
Context triple: [Manufacturing Belt, laborCharacteristic, strong labor unions]
  • A. laborProvision
    Indicates the provision or supply of labor or workforce from one party to another for work or services.
  • B. laborSystem
    Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
  • C. constructionCharacteristic
    Indicates a specific structural or material property that characterizes how something is built or constructed.
  • D. characterizedBy chosen
    Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
  • E. labour
    Indicates that an entity performs work or exerts effort, typically in a productive, economic, or physical context, often for another entity or purpose.
  • 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_69a494060e148190abb42f971242c197 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcad47a08190895769611798f67f completed March 1, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69a4bb525b648190adcb7a29256d3c41 completed March 1, 2026, 10:18 p.m.
Created at: March 1, 2026, 7:45 p.m.