Triple
T27657957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q-bus |
E697042
|
entity |
| Predicate | addressSpaceType |
P77125
|
FINISHED |
| Object | shared address and data lines |
—
|
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: shared address and data lines | Statement: [Q-bus, addressSpaceType, shared address and data lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressSpaceType Context triple: [Q-bus, addressSpaceType, shared address and data lines]
-
A.
addressSpaceSize
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
B.
spaceType
chosen
Indicates the category or kind of physical or conceptual space associated with an entity.
-
C.
addressFamily
Indicates the type of network address family (such as IPv4 or IPv6) associated with or used by an entity in a communication context.
-
D.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
-
E.
typeOfAddress
Indicates the specific category or kind of address (e.g., home, work, billing) associated with an entity.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 2:35 p.m.