Triple
T8610812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GATT |
E203908
|
entity |
| Predicate | attributeIdentifiedBy |
P82085
|
FINISHED |
| Object | handle |
—
|
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: handle | Statement: [GATT, attributeIdentifiedBy, handle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attributeIdentifiedBy Context triple: [GATT, attributeIdentifiedBy, handle]
-
A.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
attributeType
Indicates that one entity specifies the kind or category of attribute that characterizes another entity.
-
C.
representedByAttribute
chosen
Indicates that one entity serves as an attribute-based representation or characterization of another entity.
-
D.
ianaIdentifierType
Indicates that one entity specifies the type or category of an IANA (Internet Assigned Numbers Authority) identifier associated with another entity.
-
E.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ee96ac8190809817c403da2889 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.