Triple
T38284877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B Corporation certification |
E1022176
|
entity |
| Predicate | requiresVerification |
P17773
|
FINISHED |
| Object | documentation review |
—
|
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: documentation review | Statement: [B Corporation certification, requiresVerification, documentation review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresVerification Context triple: [B Corporation certification, requiresVerification, documentation review]
-
A.
requiresProofOf
chosen
Indicates that one entity must provide formal evidence or documentation to validate or authorize another entity.
-
B.
requiresProofIn
Indicates that one entity must be justified, validated, or supported by formal proof within the context or framework specified by another entity.
-
C.
confirmationRequirement
Indicates that an action, decision, or change is contingent on receiving explicit confirmation from a specified party or process.
-
D.
requiresPass
Indicates that access to or participation in something is conditional on possessing a valid pass.
-
E.
requiresCertification
Indicates that one entity can only be performed, accessed, or considered valid if another entity has an appropriate certification.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00b479c1588190af6e0698b7f8d7f7 |
completed | May 10, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_6a00b4158260819087d0cfad8b18cef4 |
completed | May 10, 2026, 4:36 p.m. |
Created at: May 3, 2026, 4:30 p.m.