Triple
T38084126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheran museums |
E950928
|
entity |
| Predicate | mayBeHousedIn |
P63637
|
FINISHED |
| Object | historic church buildings |
—
|
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: historic church buildings | Statement: [Lutheran museums, mayBeHousedIn, historic church buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeHousedIn Context triple: [Lutheran museums, mayBeHousedIn, historic church buildings]
-
A.
housedInCountry
Indicates that an entity is located, based, or situated within the boundaries of a specified country.
-
B.
sometimesLocatedIn
chosen
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
C.
housedInCity
Indicates that one entity (such as a building, organization, or facility) is located within and contained by a particular city.
-
D.
isHomeOf
Indicates that a place serves as the primary residence or base for a person, group, or organization.
-
E.
locatedInTheInteriorOf
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:21 p.m.