Triple
T30469798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolidated Edison power plant |
E775260
|
entity |
| Predicate | useAfterConversion |
P46500
|
FINISHED |
| Object | recording studio |
—
|
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: recording studio | Statement: [Consolidated Edison power plant, useAfterConversion, recording studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useAfterConversion Context triple: [Consolidated Edison power plant, useAfterConversion, recording studio]
-
A.
functionAfterConversion
chosen
Indicates that one function or behavior occurs as a result of, or is valid only after, a specified conversion has taken place.
-
B.
dedicatedToAfterConversion
Indicates that an entity becomes dedicated or committed to another entity or purpose as a result of a conversion or transformative process.
-
C.
afterConversionKnownAs
Indicates that an entity is referred to by a new name or identifier after undergoing a conversion or transformation.
-
D.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
E.
usedAfterName
Indicates that one element is used or appears immediately after a name in some context or representation.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68714edd88190a49ba653a0360961 |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:11 p.m.