Triple
T9668200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bravado |
E233757
|
entity |
| Predicate | commercialClassification |
P72821
|
FINISHED |
| Object | for-profit company |
—
|
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: for-profit company | Statement: [Bravado, commercialClassification, for-profit company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialClassification Context triple: [Bravado, commercialClassification, for-profit company]
-
A.
commercialCategory
chosen
Indicates the type of commercial classification or business category under which an entity or transaction is grouped.
-
B.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
C.
commercialActivity
Indicates an action or relationship involving the buying, selling, or exchange of goods or services for profit or other economic gain.
-
D.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
E.
commercialService
Indicates a relationship where one entity provides a paid, profit-oriented service 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3c06e4819080c1b8e66faa482f |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.