Triple
T3848271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HR |
E85225
|
entity |
| Predicate | positionInPlate |
P30243
|
FINISHED |
| Object | leading code |
—
|
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: leading code | Statement: [HR, positionInPlate, leading code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPlate Context triple: [HR, positionInPlate, leading code]
-
A.
plateLocation
chosen
Indicates the spatial position or placement of a plate relative to a reference location or object.
-
B.
positionInChamber
Indicates the specific location or role an entity holds within a particular chamber or assembly.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
positionInMass
Indicates that an entity occupies a specific location or role within a larger undifferentiated group, collection, or mass.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcc8a0481909c35161336bdfbf9 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.