Triple
T34819313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selected Acquisition Report |
E1003723
|
entity |
| Predicate | standardizedFormat |
P8032
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Selected Acquisition Report, standardizedFormat, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedFormat Context triple: [Selected Acquisition Report, standardizedFormat, yes]
-
A.
standardizedFormOf
Indicates that one entity is the normalized or officially standardized version of another, often consolidating variations or alternative forms into a single canonical form.
-
B.
standardizedFor
chosen
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
-
C.
standardizedFrom
Indicates that one entity is a standardized or normalized version derived from another entity.
-
D.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
E.
standardizedSince
Indicates that something has been formally standardized starting from a specific point in time.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4 p.m.