Triple
T1985950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GÖ |
E43140
|
entity |
| Predicate | placementOnPlate |
P3250
|
FINISHED |
| Object | prefix before random 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 random letters and numbers | Statement: [GÖ, placementOnPlate, prefix before random letters and numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placementOnPlate Context triple: [GÖ, placementOnPlate, prefix before random 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.
involvesPlate
Indicates that an event, action, or situation includes or makes use of a plate as a relevant participant or object.
-
D.
placeHeld
Indicates that an entity occupies or is located at a specific place or position.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.