Triple

T30008187
Position Surface form Disambiguated ID Type / Status
Subject Rubber Factory E762381 entity
Predicate recordingLocationNote P8088 FINISHED
Object recorded in an abandoned tire factory 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: recorded in an abandoned tire factory | Statement: [Rubber Factory, recordingLocationNote, recorded in an abandoned tire factory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recordingLocationNote
Context triple: [Rubber Factory, recordingLocationNote, recorded in an abandoned tire factory]
  • A. recordingLocationTour
    Indicates the place where a tour-related recording (such as a live performance or tour event) was made.
  • B. placeOfRecording chosen
    Indicates the location where an audio, video, or other recording was made.
  • C. recordAttemptLocation
    Indicates that an attempt is made to store or log the specific location where an event or action occurred.
  • D. recordingFor
    Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
  • E. navigationNote
    Indicates that there is an auxiliary note or instruction intended to guide or assist navigation within a resource, interface, or environment.
  • 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_69f2246a47ac81909cf5213053687ffc completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f7b5ccbda481908fe1945c35e36ce8 completed May 3, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69f7b4c06f5881908f0b98cad6796478 completed May 3, 2026, 8:49 p.m.
Created at: April 29, 2026, 6:43 p.m.