Triple
T28480813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Engineering Publications |
E720683
|
entity |
| Predicate | supportsDocumentType |
P20985
|
FINISHED |
| Object | NATO Standardization Agreement |
—
|
NE NERFINISHED |
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: NATO Standardization Agreement | Statement: [Allied Engineering Publications, supportsDocumentType, NATO Standardization Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDocumentType Context triple: [Allied Engineering Publications, supportsDocumentType, NATO Standardization Agreement]
-
A.
supportsDocument
chosen
Indicates that one entity provides compatibility or functionality for handling, processing, or using a particular document or document type.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
worksOnDocumentType
Indicates that an entity is involved in handling, processing, or performing tasks related to a specific type or category of document.
-
D.
supportsDomainType
Indicates that one entity is capable of handling, operating with, or being applicable to a specified domain type.
-
E.
documentTypeIncluded
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: April 28, 2026, 2:55 a.m.