Triple
T22322917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobo (Python web framework) |
E551829
|
entity |
| Predicate | codeFootprint |
P147733
|
FINISHED |
| Object | small codebase |
—
|
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: small codebase | Statement: [Bobo (Python web framework), codeFootprint, small codebase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeFootprint Context triple: [Bobo (Python web framework), codeFootprint, small codebase]
-
A.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
B.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
C.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
D.
engineCode
Indicates a relationship where an entity is associated with a specific engine identification code or designation.
-
E.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15765a004819081dcdccbfd0efea7 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:42 p.m.