Triple
T7893304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mojombo |
E183287
|
entity |
| Predicate | githubProfile |
P79610
|
FINISHED |
| Object | https://github.com/mojombo |
—
|
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/mojombo | Statement: [mojombo, githubProfile, https://github.com/mojombo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: githubProfile Context triple: [mojombo, githubProfile, https://github.com/mojombo]
-
A.
githubUsername
Indicates that one entity is the GitHub account username associated with another entity.
-
B.
githubOrganization
Indicates that an entity is an organization hosted on or associated with the GitHub platform.
-
C.
profileDirectory
Indicates the directory path where a user's or application's profile data is stored or managed.
-
D.
publicProfile
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
E.
mediaProfile
Indicates a relationship where a media-related profile or account is associated with an entity, typically representing its presence or identity in media contexts.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a008fb88190a039fec40483ab93 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 5 p.m.