Triple
T29388321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generic Attribute Profile |
E745308
|
entity |
| Predicate | attributeAddressing |
P64006
|
FINISHED |
| Object | attribute handles |
—
|
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: attribute handles | Statement: [Generic Attribute Profile, attributeAddressing, attribute handles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attributeAddressing Context triple: [Generic Attribute Profile, attributeAddressing, attribute handles]
-
A.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
-
B.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
C.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
D.
addressingMechanism
chosen
Indicates the method or system used to identify, locate, or reference a target within a larger space, network, or structure.
-
E.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d44b7c8190a79e108c68a7077a |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:40 p.m.