Triple
T2337384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HH |
E44341
|
entity |
| Predicate | positionOnPlate |
P3250
|
FINISHED |
| Object | prefix before serial letters and numbers |
—
|
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: prefix before serial letters and numbers | Statement: [HH, positionOnPlate, prefix before serial letters and numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnPlate Context triple: [HH, positionOnPlate, prefix before serial letters and numbers]
-
A.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
-
B.
positionOn
chosen
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
positionOnGood
Indicates the stance or viewpoint an entity holds regarding a particular good, such as support, opposition, or neutrality.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.