Triple
T29867409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gbXML |
E758493
|
entity |
| Predicate | supportsUnitsSpecification |
P207188
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [gbXML, supportsUnitsSpecification, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsUnitsSpecification Context triple: [gbXML, supportsUnitsSpecification, true]
-
A.
supportedUnit
Indicates that one entity provides assistance, resources, or backing to another entity functioning as a unit or sub-organization.
-
B.
basedUnitsInclude
Indicates that a composite or derived unit is defined using, and therefore includes, the specified base unit(s) in its construction.
-
C.
typicalSupportedUnitType
Indicates the kind or category of unit that an entity is normally designed or expected to support.
-
D.
hasUnits
Indicates that a quantity, measurement, or value is expressed in a specified system or type of units.
-
E.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 5:52 p.m.