Triple
T13070052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G22/G23/G26 |
E329431
|
entity |
| Predicate | bodyCode |
P108286
|
FINISHED |
| Object | G22 |
—
|
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: G22 | Statement: [G22/G23/G26, bodyCode, G22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyCode Context triple: [G22/G23/G26, bodyCode, G22]
-
A.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
B.
fullCode
Indicates that an entity is represented by a complete, fully specified code rather than a partial or abbreviated one.
-
C.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
D.
codeSection
Indicates a specific segment or subsection within a larger body of code that is distinguished for reference, organization, or analysis.
-
E.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ee6130819095d835e7ff6a8c5b |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d980e622e8819087a69bfb1660dd64 |
completed | April 10, 2026, 10:59 p.m. |
Created at: April 9, 2026, 9 p.m.