Triple
T37666146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cap Kingdom |
E937822
|
entity |
| Predicate | revisitable |
P182915
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cap Kingdom, revisitable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisitable Context triple: [Cap Kingdom, revisitable, yes]
-
A.
revisitability
chosen
Indicates the degree to which something can or is likely to be visited again, often based on its appeal, accessibility, or enduring relevance.
-
B.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
C.
reversibility
Indicates that a process, action, or transformation can be undone or reversed to restore the original state or conditions.
-
D.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
E.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e16fb881908bb74df86ab04427 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.