Triple
T3426370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BSD license |
E72237
|
entity |
| Predicate | mayIncludeClause |
P12721
|
FINISHED |
| Object | advertising clause |
—
|
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: advertising clause | Statement: [BSD license, mayIncludeClause, advertising clause]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeClause Context triple: [BSD license, mayIncludeClause, advertising clause]
-
A.
includesClause
chosen
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
B.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
C.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
D.
mayIncludeJudgeAdHoc
Indicates that an entity is permitted to include a judge appointed on an ad hoc (temporary or case-specific) basis.
-
E.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9812a648190ac919e7291744b5a |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.