Triple
T26818464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C2r |
E675180
|
entity |
| Predicate | chronNumber |
P168579
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [C2r, chronNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronNumber Context triple: [C2r, chronNumber, 2]
-
A.
inscriptionNumber
Indicates the identifying number assigned to a specific inscription within a collection or system.
-
B.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
-
C.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
D.
categoryNumbering
Indicates that items within a category are assigned an ordered or structured numbering scheme that defines their position or sequence in that category.
-
E.
chronRank
Indicates the relative chronological order or ranking of events or time-related entities with respect to one another.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 4:53 a.m.