Triple
T38040716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kripke frame |
E949472
|
entity |
| Predicate | canHaveProperty |
P189898
|
FINISHED |
| Object | reflexive accessibility relation |
—
|
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: reflexive accessibility relation | Statement: [Kripke frame, canHaveProperty, reflexive accessibility relation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHaveProperty Context triple: [Kripke frame, canHaveProperty, reflexive accessibility relation]
-
A.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
B.
hasPropertyT
Indicates that an entity possesses or is characterized by a specific property T.
-
C.
requiresProperty
Indicates that one entity depends on another entity possessing a specific property or attribute in order for a condition, action, or relationship to hold.
-
D.
usesProp
Indicates that one entity employs, utilizes, or makes use of a particular property, resource, or object in performing an action or fulfilling a function.
-
E.
hasSignProperty
Indicates that an entity possesses a specific sign-related characteristic or attribute.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:20 p.m.