Triple
T6442848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adoro te devote |
E138265
|
entity |
| Predicate | hasEnglishParaphrase |
P31361
|
FINISHED |
| Object | Humbly I Adore Thee |
—
|
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: Humbly I Adore Thee | Statement: [Adoro te devote, hasEnglishParaphrase, Humbly I Adore Thee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnglishParaphrase Context triple: [Adoro te devote, hasEnglishParaphrase, Humbly I Adore Thee]
-
A.
hasEnglishEdition
Indicates that one entity has a version or edition of itself that is produced or available in the English language.
-
B.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
C.
languageEquivalent
Indicates that two linguistic expressions convey the same meaning or function across different languages or language varieties.
-
D.
EnglishTranslation
chosen
Indicates that one expression is the English-language translation equivalent of another expression.
-
E.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.