Triple
T16747075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSAP |
E406983
|
entity |
| Predicate | hasBit |
P124484
|
FINISHED |
| Object | Individual/Group (I/G) bit |
—
|
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: Individual/Group (I/G) bit | Statement: [DSAP, hasBit, Individual/Group (I/G) bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBit Context triple: [DSAP, hasBit, Individual/Group (I/G) bit]
-
A.
hasSignatureBit
Indicates that an entity possesses a specific bit or flag used to represent a signature or signed status in a data structure or encoding.
-
B.
hasCap
Indicates that an entity possesses or is equipped with a cap or top covering.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
E.
hasBinary
Indicates that one entity is associated with another entity in a binary (two-component) relationship, typically as one of the two members of a pair.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.