Triple
T22343946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIL |
E552342
|
entity |
| Predicate | hasCatalogNumberingSystem |
P5213
|
FINISHED |
| Object | CIL inscription numbers |
—
|
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: CIL inscription numbers | Statement: [CIL, hasCatalogNumberingSystem, CIL inscription numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogNumberingSystem Context triple: [CIL, hasCatalogNumberingSystem, CIL inscription numbers]
-
A.
hasCabinetNumberingSystem
Indicates that there is a specific scheme or method used to assign and organize identification numbers to cabinets.
-
B.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
C.
usesHarmonizedNumberingWith
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
-
D.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
E.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15796b2288190b10e9402abf35fd3 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.