Triple
T31762041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSC |
E810705
|
entity |
| Predicate | isVendorSpecificCode |
P116114
|
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: [FTSC, isVendorSpecificCode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVendorSpecificCode Context triple: [FTSC, isVendorSpecificCode, true]
-
A.
hasDataVendorCode
Indicates that an entity is associated with a specific vendor-assigned code used to identify its data source or provider.
-
B.
isVendorNeutral
Indicates that something is not biased toward, affiliated with, or dependent on any particular vendor or supplier.
-
C.
vendorSpecific
chosen
Indicates that something is defined, implemented, or applicable only for a particular vendor, rather than being generic or standardized.
-
D.
isOfficialCodeFor
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
-
E.
hasTypeOfVendor
Indicates that an entity is associated with or classified under a specific category or type of vendor.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab81a81c81908236f2956569b4a8 |
completed | May 3, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:31 p.m.