Triple
T21531269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nones |
E531234
|
entity |
| Predicate | relationToIdes |
P34778
|
FINISHED |
| Object | 9 days before the Ides (inclusive count) |
—
|
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: 9 days before the Ides (inclusive count) | Statement: [Nones, relationToIdes, 9 days before the Ides (inclusive count)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToIdes Context triple: [Nones, relationToIdes, 9 days before the Ides (inclusive count)]
-
A.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
-
B.
termRelationTo
chosen
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
C.
relationToCurie
Indicates a relational connection or association that one entity has specifically with Curie.
-
D.
relatedIdentity
Indicates that two identities are connected or associated with each other in some meaningful way, such as being alternate, linked, or otherwise contextually related.
-
E.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d08ebf881909574e098404f93fa |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.