Triple
T36036597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farmington Police Department |
E1042418
|
entity |
| Predicate | buildingTypeInSeries |
P1844
|
FINISHED |
| Object | converted church |
—
|
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: converted church | Statement: [Farmington Police Department, buildingTypeInSeries, converted church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingTypeInSeries Context triple: [Farmington Police Department, buildingTypeInSeries, converted church]
-
A.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
eraOfManyBuildings
Indicates a time period during which many buildings were constructed or existed.
-
C.
builtType
Indicates the structural or construction type characterizing how something is built or formed.
-
D.
buildingTypeServed
Indicates the type of building that is served, supported, or catered to by a given entity or system.
-
E.
buildingSystem
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:07 p.m.