Triple
T34954828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TeX82 |
E1008097
|
entity |
| Predicate | bugPolicy |
P116336
|
FINISHED |
| Object | only bug fixes allowed |
—
|
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: only bug fixes allowed | Statement: [TeX82, bugPolicy, only bug fixes allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bugPolicy Context triple: [TeX82, bugPolicy, only bug fixes allowed]
-
A.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
B.
ethicalPolicy
Indicates that an entity has, follows, or is governed by a specified ethical policy or set of moral guidelines.
-
C.
publicPolicy
Indicates that an entity is a government or institutional rule, principle, or course of action intended to address public issues or guide societal outcomes.
-
D.
explainsPolicy
Indicates that one entity provides a clarification or detailed description of a policy to another entity.
-
E.
usagePolicy
chosen
Indicates the rules or conditions governing how something may be used or accessed.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.