Triple
T3238670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars |
E67915
|
entity |
| Predicate | sacredTree |
P47537
|
FINISHED |
| Object | oak |
—
|
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: oak | Statement: [Mars, sacredTree, oak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredTree Context triple: [Mars, sacredTree, oak]
-
A.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
B.
sacredTruce
Indicates a formally recognized period during which hostilities or conflicts are suspended, often for religious or ceremonial reasons.
-
C.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
D.
sacredTankName
Indicates that an entity has a name identifying it as a sacred or holy water tank or reservoir.
-
E.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaef3b04081908ce9b788e2e5c63c |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada698eeb48190a1f5762fdd3b7b63 |
completed | March 8, 2026, 4:40 p.m. |
Created at: March 8, 2026, 3:08 p.m.