Triple
T4110096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claros |
E88550
|
entity |
| Predicate | oraclePractice |
P10364
|
FINISHED |
| Object | consultation by priests in underground chamber |
—
|
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: consultation by priests in underground chamber | Statement: [Claros, oraclePractice, consultation by priests in underground chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oraclePractice Context triple: [Claros, oraclePractice, consultation by priests in underground chamber]
-
A.
oracleType
Indicates the specific kind or category of oracle associated with or used by an entity.
-
B.
linkedToOracle
Indicates that one entity is connected or associated with an Oracle system, service, or resource.
-
C.
usedInDatabases
Indicates that something is employed or implemented within one or more database systems or database contexts.
-
D.
hibernates
Indicates that an entity spends a prolonged period in a dormant, low-activity state, typically to survive unfavorable environmental conditions.
-
E.
isPracticedBy
chosen
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.