Triple
T17389302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsea |
E422772
|
entity |
| Predicate | keyFunctionInVolturi |
P23210
|
FINISHED |
| Object | maintaining loyalty within the Volturi |
—
|
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: maintaining loyalty within the Volturi | Statement: [Chelsea, keyFunctionInVolturi, maintaining loyalty within the Volturi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyFunctionInVolturi Context triple: [Chelsea, keyFunctionInVolturi, maintaining loyalty within the Volturi]
-
A.
keyFunction
chosen
Indicates that an entity serves as a primary or essential mechanism enabling a particular operation, role, or outcome for another entity.
-
B.
keyVow
Indicates a formal promise or commitment that is central or essential to an agreement, relationship, or situation.
-
C.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
D.
keyInvocation
Indicates that an entity triggers or calls a specific key-related operation or function.
-
E.
keyFormula
Indicates that a formula serves as the primary or defining expression associated with an entity or relationship.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a8c718c81909cb20749aaf12897 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.