Triple
T13907184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameron Gallery |
E334383
|
entity |
| Predicate | upperLevelFunction |
P63202
|
FINISHED |
| Object | open gallery for walking |
—
|
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: open gallery for walking | Statement: [Cameron Gallery, upperLevelFunction, open gallery for walking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperLevelFunction Context triple: [Cameron Gallery, upperLevelFunction, open gallery for walking]
-
A.
hasUpperLevelFunction
chosen
Indicates that one function operates at a higher or more abstract level than another function within a hierarchical relationship.
-
B.
higherLevelBody
Indicates that one body or organizational unit functions at a higher or more encompassing level of authority or structure relative to another.
-
C.
upperLevelConnects
Indicates a connection where one entity links to or interfaces with another at a higher or superior level in a hierarchy or structure.
-
D.
upperCourseOf
Indicates that one watercourse represents the upstream or higher-elevation segment of another watercourse within the same river system.
-
E.
laterFunction
Indicates that one function or event occurs after another in time.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25dc26cc8190a7909980b1d34933 |
completed | April 14, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.