Triple
T18300805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farama Foundation |
E438351
|
entity |
| Predicate | github |
P55144
|
FINISHED |
| Object | https://github.com/Farama-Foundation |
—
|
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: https://github.com/Farama-Foundation | Statement: [Farama Foundation, github, https://github.com/Farama-Foundation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: github Context triple: [Farama Foundation, github, https://github.com/Farama-Foundation]
-
A.
codeHostingService
chosen
Indicates a relationship where a platform provides hosting and management services for source code repositories and related development workflows.
-
B.
githubUsername
Indicates that one entity is the GitHub account username associated with another entity.
-
C.
githubOrganization
Indicates that an entity is an organization hosted on or associated with the GitHub platform.
-
D.
githubProfile
Indicates that an entity has a GitHub user profile associated with it.
-
E.
roleAtGitHub
Indicates the specific position, title, or function an entity holds within GitHub.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017f63dc819083a675d570620f2f |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.