Triple
T5387298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Definition |
E120230
|
entity |
| Predicate | licenseCompatibilityCriterion |
P34363
|
FINISHED |
| Object | must allow commercial use |
—
|
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: must allow commercial use | Statement: [Open Definition, licenseCompatibilityCriterion, must allow commercial use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseCompatibilityCriterion Context triple: [Open Definition, licenseCompatibilityCriterion, must allow commercial use]
-
A.
checksCompatibilityWith
Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
-
B.
licenseListIncludes
Indicates that a specified license list contains or covers a particular license or licensing term.
-
C.
requiresCompatibilityWith
chosen
Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
-
D.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
-
E.
licenseBuiltIn
Indicates that a license is inherently included within or comes standard as part of another product, service, or system rather than being added separately.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f8d81081909174027a4fe640f2 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.