Triple
T10054048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmonized System |
E208817
|
entity |
| Predicate | allowsExtensionBy |
P11253
|
FINISHED |
| Object | national tariff lines |
—
|
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: national tariff lines | Statement: [Harmonized System, allowsExtensionBy, national tariff lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsExtensionBy Context triple: [Harmonized System, allowsExtensionBy, national tariff lines]
-
A.
hasExtensionBy
Indicates that one entity is extended, augmented, or further developed by another entity.
-
B.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
C.
supportsExtensionsFrom
Indicates that one entity is capable of recognizing, loading, or interoperating with extensions originating from another entity.
-
D.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
-
E.
extensionMechanism
chosen
Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfab39408190ac728fe156eed658 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.