Triple
T3207244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaldeans |
E67192
|
entity |
| Predicate | termAlsoUsedFor |
P46176
|
FINISHED |
| Object | Babylonian astrologer-priests |
—
|
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: Babylonian astrologer-priests | Statement: [Chaldeans, termAlsoUsedFor, Babylonian astrologer-priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termAlsoUsedFor Context triple: [Chaldeans, termAlsoUsedFor, Babylonian astrologer-priests]
-
A.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
B.
isAlsoUsedAs
Indicates that something serves an additional function or role beyond its primary one.
-
C.
notPreferredTermFor
Indicates that one term is a non-preferred or deprecated label that should be replaced by another, preferred term in a controlled vocabulary or terminology system.
-
D.
languageTerm
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
-
E.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
- F. None of above. chosen
Provenance (4 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa58340881908347d772cfa0ac4c |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.