Triple
T26818465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C2r |
E675180
|
entity |
| Predicate | chronSubunit |
P157303
|
FINISHED |
| Object | r |
—
|
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: r | Statement: [C2r, chronSubunit, r]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronSubunit Context triple: [C2r, chronSubunit, r]
-
A.
chronNumber
Indicates that one entity is assigned a specific chronological number or position in an ordered sequence relative to others.
-
B.
chronologyWithinSubseries
chosen
Indicates that one entity occurs in chronological order within the temporal sequence defined by a specific subseries.
-
C.
minorUnitSubdivisions
Indicates that one administrative or organizational unit is subdivided into smaller, subordinate units.
-
D.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
E.
typicalSubunitOf
Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 4:53 a.m.