Triple
T28610751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRIS |
E724161
|
entity |
| Predicate | isaFamily |
P164913
|
FINISHED |
| Object | CRIS instruction set architecture |
—
|
NE NERFINISHED |
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: CRIS instruction set architecture | Statement: [CRIS, isaFamily, CRIS instruction set architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isaFamily Context triple: [CRIS, isaFamily, CRIS instruction set architecture]
-
A.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
B.
fareFamily
Indicates a relationship that classifies a fare or ticket into a specific fare family or category within a pricing structure.
-
C.
topFamily
Indicates that the subject entity belongs to the highest-ranking or primary family group within a given hierarchy or classification.
-
D.
familia
Indicates a familial relationship or bond between entities, such as being members of the same family.
-
E.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:30 a.m.