Triple
T4689458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICPC |
E103998
|
entity |
| Predicate | codingUnit |
P58808
|
FINISHED |
| Object | episode of care |
—
|
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: episode of care | Statement: [ICPC, codingUnit, episode of care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codingUnit Context triple: [ICPC, codingUnit, episode of care]
-
A.
definesUnit
Indicates that one entity specifies the measurement unit or standard by which the value or quantity of another entity is expressed.
-
B.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
-
C.
componentUnit
Indicates that one entity functions as a constituent or sub-unit that forms part of a larger composite entity.
-
D.
unit
Indicates that two quantities are measured using the same standard unit of measurement.
-
E.
BOMCodeUnit
Indicates a relationship where a bill of materials (BOM) is associated with a specific code unit that defines or implements its structure, logic, or processing.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd660414b08190ab37467755d383b5 |
completed | March 20, 2026, 3:21 p.m. |
Created at: March 20, 2026, 1:16 p.m.