Triple
T21736556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Cody |
E536539
|
entity |
| Predicate | hasInnerState |
P107449
|
FINISHED |
| Object | inner turmoil |
—
|
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: inner turmoil | Statement: [Pope Cody, hasInnerState, inner turmoil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInnerState Context triple: [Pope Cody, hasInnerState, inner turmoil]
-
A.
innerState
chosen
Indicates a relationship where an entity’s internal condition, feeling, or mental/emotional status is specified or characterized.
-
B.
hasCoreState
Indicates that an entity possesses or is associated with a fundamental or primary state that defines its core condition or behavior.
-
C.
hasStateSystem
Indicates that an entity possesses, follows, or is governed by a particular system of state organization, rules, or governance.
-
D.
hasStateBranch
Indicates that one entity functions as a branch, subdivision, or local office of a larger parent entity within a particular state or regional jurisdiction.
-
E.
hasInitialState
Indicates that an entity begins or is configured with a specified starting condition 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd0c0a088190bd1926fa4b73d8f4 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.