Triple
T38284891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B Corporation certification |
E1022176
|
entity |
| Predicate | feeStructureDependsOn |
P190608
|
FINISHED |
| Object | company size |
—
|
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: company size | Statement: [B Corporation certification, feeStructureDependsOn, company size]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeStructureDependsOn Context triple: [B Corporation certification, feeStructureDependsOn, company size]
-
A.
fareStructure
Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
-
B.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
C.
feeAppliesTo
Indicates that a particular fee is charged in connection with, or is applicable to, a specified item, service, or transaction.
-
D.
fareStructureFeature
Indicates a characteristic or condition of how fares are structured, calculated, or applied within a pricing or ticketing system.
-
E.
feeComponents
Indicates that a fee is composed of one or more sub-fees or cost elements that together make up the total charge.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.