Triple
T21581581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entity List |
E532535
|
entity |
| Predicate | licenseReviewPolicy |
P144351
|
FINISHED |
| Object | case-by-case 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: case-by-case review | Statement: [Entity List, licenseReviewPolicy, case-by-case review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseReviewPolicy Context triple: [Entity List, licenseReviewPolicy, case-by-case review]
-
A.
licenseEnforced
Indicates that a license’s terms or restrictions are actively applied and upheld in relation to the associated entity or activity.
-
B.
licenseStewardship
Indicates that one entity is responsible for managing, overseeing, or administering a license on behalf of another entity.
-
C.
licensePreference
Indicates a party’s chosen or prioritized type of license to use, grant, or operate under in a given context.
-
D.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
E.
licenseStatus
Indicates the current state or condition of a license in relation to its validity, permissions, or compliance.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5d28e08190a38de7ad7ed12743 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:31 p.m.