Triple
T27657670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R6 (stack pointer) |
E697036
|
entity |
| Predicate | registerNumber |
P163936
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [R6 (stack pointer), registerNumber, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerNumber Context triple: [R6 (stack pointer), registerNumber, 6]
-
A.
registrationNumber
Indicates the unique identifier assigned to an entity as part of an official or formal registration process.
-
B.
inscriptionNumber
Indicates the identifying number assigned to a specific inscription within a collection or system.
-
C.
nameNumber
Indicates a relationship where a specific name is associated with a particular numerical identifier or value.
-
D.
ayahNumber
Indicates the specific verse number assigned to an ayah within a surah or text.
-
E.
alternateNumber
Indicates that one entity serves as an alternative or secondary number (such as a phone or contact number) for another entity.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 2:35 p.m.