Triple
T36036596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farmington Police Department |
E1042418
|
entity |
| Predicate | hasNickNameInSeries |
P149399
|
FINISHED |
| Object | The Barn |
—
|
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: The Barn | Statement: [Farmington Police Department, hasNickNameInSeries, The Barn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNickNameInSeries Context triple: [Farmington Police Department, hasNickNameInSeries, The Barn]
-
A.
partOfNicknameSeriesFor
Indicates that one nickname belongs to a series or set of related nicknames associated with the same entity.
-
B.
hasNicknames
chosen
Indicates that an entity is known or referred to by one or more alternative informal names.
-
C.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
D.
hasNicknamedEntityType
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
-
E.
fictionalNameInSeries
Indicates that a fictional character is known by a particular name within a specific narrative series or franchise.
- 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_69f7ad1bf27081909683fa99a367f556 |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.