Triple
T16986991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACS Award in Organometallic Chemistry |
E412092
|
entity |
| Predicate | typicalRecognition |
P98372
|
FINISHED |
| Object | formal citation |
—
|
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: formal citation | Statement: [ACS Award in Organometallic Chemistry, typicalRecognition, formal citation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRecognition Context triple: [ACS Award in Organometallic Chemistry, typicalRecognition, formal citation]
-
A.
typicalRecognitionFormat
chosen
Indicates the usual or standard format in which something is recognized, identified, or acknowledged.
-
B.
recognizableFor
Indicates that one entity is known or identifiable because of a particular characteristic, feature, or association with another entity.
-
C.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
-
D.
canRecognize
Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
-
E.
primaryRecognition
Indicates that one entity is the main or foremost source of acknowledgment, credit, or validation for another entity.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27b58908190a643bcbd105b1849 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.