Triple
T338017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chi-Rho monogram |
E6770
|
entity |
| Predicate | derivesFromWord |
P909
|
FINISHED |
| Object | Greek word "Χριστός" |
—
|
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: Greek word "Χριστός" | Statement: [Chi-Rho monogram, derivesFromWord, Greek word "Χριστός"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivesFromWord Context triple: [Chi-Rho monogram, derivesFromWord, Greek word "Χριστός"]
-
A.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
kun’yomiDerivedFrom
Indicates that a Japanese kun’yomi (native Japanese reading of a kanji) originates from or is historically derived from another form, source, or expression.
-
C.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
D.
differentiatedFrom
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
E.
cognateOf
Indicates that two linguistic forms share a common historical origin, typically descending from the same ancestral word.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae23b0c819081f8bf9ac26685ab |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.