Triple
T25436552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XD bit |
E637386
|
entity |
| Predicate | bitLocation |
P158514
|
FINISHED |
| Object | page table entry |
—
|
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: page table entry | Statement: [XD bit, bitLocation, page table entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitLocation Context triple: [XD bit, bitLocation, page table entry]
-
A.
binaryLocation
Indicates that one entity is the physical or logical location where another binary or executable artifact resides.
-
B.
segmentLocation
Indicates the spatial or positional relationship specifying where a particular segment is located within a larger structure or context.
-
C.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
D.
biteLocationPreference
Indicates a tendency or pattern regarding where on a target an entity prefers to bite.
-
E.
bendLocation
Indicates the location at which something bends, curves, or changes direction.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6e0338c8190ace22e7a6239f68d |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:59 p.m.