Triple
T264665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GitHub |
E5697
|
entity |
| Predicate | supportsLicenseModel |
P5098
|
FINISHED |
| Object | free tier |
—
|
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: free tier | Statement: [GitHub, supportsLicenseModel, free tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLicenseModel Context triple: [GitHub, supportsLicenseModel, free tier]
-
A.
licenseFamily
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
B.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
supportsAccountType
chosen
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
E.
supportsClaim
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.