Triple
T7279662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 8080 |
E163113
|
entity |
| Predicate | registerPair |
P76207
|
FINISHED |
| Object | BC |
—
|
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: BC | Statement: [Intel 8080, registerPair, BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerPair Context triple: [Intel 8080, registerPair, BC]
-
A.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
-
B.
commonPair
Indicates that two entities commonly occur together or are frequently associated as a pair in some shared context.
-
C.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
D.
starPairing
Indicates a relationship where two stars are associated or grouped together as a pair, typically for observational, analytical, or classificatory purposes.
-
E.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 2:59 p.m.