Triple
T31174304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Β |
E794698
|
entity |
| Predicate | hasHTMLCode |
P171215
|
FINISHED |
| Object | Β |
—
|
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: Β | Statement: [Β, hasHTMLCode, Β]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHTMLCode Context triple: [Β, hasHTMLCode, Β]
-
A.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
B.
hasCodeElementsFor
Indicates a relationship where one entity contains, defines, or is associated with specific code elements (such as classes, methods, or functions) that implement or support another entity.
-
C.
hasScriptCode
Indicates that an entity is associated with a particular writing system identified by a specific script code.
-
D.
hasCodeBrowser
Indicates that an entity provides or is associated with a tool or interface for browsing and viewing source code.
-
E.
hasIneCode
Indicates that an entity is associated with a specific INE (national statistics or education) code that identifies it in an official registry.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6f01e881908fa84f5d429d37ae |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:07 p.m.