Triple
T5528819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | October |
E144994
|
entity |
| Predicate | containsScorpioDatesApprox |
P34156
|
FINISHED |
| Object | October 23–31 |
—
|
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: October 23–31 | Statement: [October, containsScorpioDatesApprox, October 23–31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsScorpioDatesApprox Context triple: [October, containsScorpioDatesApprox, October 23–31]
-
A.
isZodiacConstellation
Indicates that one entity is a constellation that belongs to the set of zodiac constellations through which the Sun appears to move over the course of a year.
-
B.
startDateTropicalZodiac
chosen
Indicates the calendar date on which a given tropical zodiac sign begins.
-
C.
isSpurOf
Indicates that one entity is a secondary offshoot, branch, or derivative extension originating from another primary entity.
-
D.
occursOnOrAround
Indicates that an event or action takes place on a specific date or within a small, approximate time window surrounding that date.
-
E.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f8b6c348190b7d414dc1907d09a |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.