Triple
T37986803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pinos area |
E947709
|
entity |
| Predicate | consideredByChumashAs |
P189826
|
FINISHED |
| Object | center of the world |
—
|
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: center of the world | Statement: [Mount Pinos area, consideredByChumashAs, center of the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredByChumashAs Context triple: [Mount Pinos area, consideredByChumashAs, center of the world]
-
A.
consideredMitzvahIn
Indicates that an action or practice is regarded as a mitzvah (a religiously commanded or meritorious deed) within a specified context, system, or tradition.
-
B.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
C.
consideredIn
Indicates that one entity is taken into account, examined, or included as a factor within the context, scope, or decision framework of another entity.
-
D.
alsoConsidered
Indicates that one item is regarded as an alternative or additional option alongside another in a given context.
-
E.
consideredByCrowleyAs
Indicates that one entity is regarded or judged in a particular way by Crowley.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.