Triple
T36332035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HHA: SP |
E894674
|
entity |
| Predicate | fullCodeWithOperator |
P85320
|
FINISHED |
| Object | HHA: SP |
—
|
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: HHA: SP | Statement: [HHA: SP, fullCodeWithOperator, HHA: SP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullCodeWithOperator Context triple: [HHA: SP, fullCodeWithOperator, HHA: SP]
-
A.
operatorCode
Indicates that one entity is associated with a specific operator’s identifying code used to denote who performs or manages an operation or service.
-
B.
fullCode
chosen
Indicates that an entity is represented by a complete, fully specified code rather than a partial or abbreviated one.
-
C.
coreOperator
Indicates that an entity functions as a primary or central operator responsible for executing or managing a core operation within a system or process.
-
D.
operationCodeName
Indicates that an operation is associated with a specific code name used to identify or refer to it.
-
E.
involvesOperator
Indicates that a given process, action, or relationship includes or makes use of a specific operator as a participating element.
- 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.