Triple
T36419355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | exarchate |
E897106
|
entity |
| Predicate | mayBePersonal |
P86594
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [exarchate, mayBePersonal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBePersonal Context triple: [exarchate, mayBePersonal, true]
-
A.
isPersonalTo
chosen
Indicates that something is uniquely associated with, belonging to, or intended for a specific individual, rather than being general or shared.
-
B.
mayBePermanent
Indicates that the relationship or condition could be lasting indefinitely but is not guaranteed to be so.
-
C.
isPersonalAppointment
Indicates that an appointment is scheduled for an individual’s personal matters rather than for professional, public, or organizational purposes.
-
D.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
E.
mayBeMarried
Indicates that two entities have a possible marital relationship, but it is not confirmed as definite.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:10 p.m.