Triple
T35255048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C III R for King Charles III |
E1018207
|
entity |
| Predicate | meaningOfC |
P126081
|
FINISHED |
| Object | Charles |
—
|
NE NERFINISHED |
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: Charles | Statement: [C III R for King Charles III, meaningOfC, Charles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfC Context triple: [C III R for King Charles III, meaningOfC, Charles]
-
A.
CISMeaning
Indicates that one concept, term, or symbol conveys, expresses, or stands for a particular meaning or interpretation in a given context.
-
B.
meaningOfChoes
Indicates a relationship where something expresses, represents, or defines the meaning or significance of a choice or set of choices.
-
C.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
D.
nodeMeaning
chosen
Indicates that one entity represents, defines, or conveys the semantic content or intended meaning of another entity.
-
E.
deviceMeaning
Indicates that one entity specifies or conveys the functional meaning, purpose, or interpretation of a device-related entity.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.