Triple
T760375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillaume |
E16054
|
entity |
| Predicate | hasMeaningGloss |
P8493
|
FINISHED |
| Object | “resolute protector” |
—
|
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: “resolute protector” | Statement: [Guillaume, hasMeaningGloss, “resolute protector”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningGloss Context triple: [Guillaume, hasMeaningGloss, “resolute protector”]
-
A.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
B.
sourceLanguageMeaning
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
C.
meaningOfPhrase
chosen
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
D.
meaningComponent
Indicates that one entity represents a semantic or conceptual component contributing to the overall meaning of another entity.
-
E.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a68158508190998da10e69252662 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a5048a8081908d0542214142664a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.