Triple
T38040734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kripke frame |
E949472
|
entity |
| Predicate | hasAccessibilityRelationType |
P33476
|
FINISHED |
| Object | binary relation on W × W |
—
|
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: binary relation on W × W | Statement: [Kripke frame, hasAccessibilityRelationType, binary relation on W × W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessibilityRelationType Context triple: [Kripke frame, hasAccessibilityRelationType, binary relation on W × W]
-
A.
hasArchitecturalRelation
Indicates a structural or spatial relationship between architectural elements, such as how buildings, components, or spaces are connected, arranged, or influence one another.
-
B.
valueAccessibility
Indicates how easily or readily a value can be obtained, used, or understood by relevant parties.
-
C.
hasRelation
chosen
Indicates that there exists some specified relationship or association between two entities.
-
D.
hasAccessibleAccess
Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
-
E.
supportsRelationType
Indicates that one entity provides assistance, endorsement, or structural backing to another entity in the context of a specified relation type.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:20 p.m.