Triple
T32709341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Distribution License |
E836355
|
entity |
| Predicate | hasRestrictionLevel |
P203998
|
FINISHED |
| Object | minimal restrictions |
—
|
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: minimal restrictions | Statement: [Eclipse Distribution License, hasRestrictionLevel, minimal restrictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestrictionLevel Context triple: [Eclipse Distribution License, hasRestrictionLevel, minimal restrictions]
-
A.
hasTierRestriction
Indicates that an entity is limited or governed by specific access or service tiers, restricting what applies at each tier.
-
B.
hasHumanUseRestriction
Indicates that there is a limitation or condition on how something may be used by humans.
-
C.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
-
D.
hasClearanceRestriction
Indicates that an entity’s access or clearance is limited or constrained by specific restrictions or conditions.
-
E.
hasMoreRestrictionsThan
Indicates that one entity is subject to a greater number or stricter set of limitations, rules, or constraints than another entity.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0308a4591081909018e2ba5d70096e |
completed | May 12, 2026, 11:01 a.m. |
| PD | Predicate disambiguation | batch_6a03079299708190a2ecaf14d3f06f48 |
completed | May 12, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_6a0308a3b03c8190b7fc9553afe06cb5 |
completed | May 12, 2026, 11:01 a.m. |
Created at: May 1, 2026, 1:10 a.m.