Triple
T11116330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In This House, On This Morning |
E262892
|
entity |
| Predicate | exploresStructureOf |
P97030
|
FINISHED |
| Object | church service |
—
|
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: church service | Statement: [In This House, On This Morning, exploresStructureOf, church service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresStructureOf Context triple: [In This House, On This Morning, exploresStructureOf, church service]
-
A.
internalStructure
Indicates that one entity is a component, part, or substructure contained within the overall structure of another entity.
-
B.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
C.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
D.
featuresStructure
Indicates that one entity possesses, exhibits, or incorporates a particular structure as a notable characteristic or component.
-
E.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
- F. None of above. chosen
Provenance (4 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa81d8c81908a387b56cbcc9128 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750cb26f48190a134614d0aa8e283 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.