Triple
T30541136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farnham, Quebec |
E777282
|
entity |
| Predicate | isRecordingLocationFor |
P8088
|
FINISHED |
| Object | Neon Bible |
—
|
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: Neon Bible | Statement: [Farnham, Quebec, isRecordingLocationFor, Neon Bible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecordingLocationFor Context triple: [Farnham, Quebec, isRecordingLocationFor, Neon Bible]
-
A.
isLandmarkRecordingIn
Indicates that a particular recording is recognized as a landmark or historically significant recording within a specified context or collection.
-
B.
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.
-
C.
mayBeRecordedAs
Indicates that something can optionally be documented or stored in a recorded form, but is not required to be.
-
D.
placeOfRecording
chosen
Indicates the location where an audio, video, or other recording was made.
-
E.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6888a17548190aee3ce11d8534270 |
completed | May 2, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:19 p.m.