Triple
T28606160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian Project Secretary |
E724055
|
entity |
| Predicate | hasTermDefinedIn |
P173342
|
FINISHED |
| Object | Debian Constitution |
—
|
NE NERFINISHED |
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: Debian Constitution | Statement: [Debian Project Secretary, hasTermDefinedIn, Debian Constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTermDefinedIn Context triple: [Debian Project Secretary, hasTermDefinedIn, Debian Constitution]
-
A.
hasTerm
Indicates that an entity includes, is associated with, or is defined by a specific term or condition.
-
B.
definedInTerm
chosen
Indicates that one entity is defined or formally specified within the scope or content of a particular term.
-
C.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
D.
hasCanonicalTerm
Indicates that one term in a set is designated as the standard or authoritative form used to represent a concept or entity.
-
E.
hasCustomTerm
Indicates that an entity is associated with a user-defined or non-standard term specific to a particular context or configuration.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:27 a.m.