Triple
T30326142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free FM |
E771344
|
entity |
| Predicate | formatStrategy |
P173748
|
FINISHED |
| Object | personality-driven talk |
—
|
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: personality-driven talk | Statement: [Free FM, formatStrategy, personality-driven talk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatStrategy Context triple: [Free FM, formatStrategy, personality-driven talk]
-
A.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
B.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
C.
formatAfter
Indicates that one entity’s format or structural arrangement is derived from, follows, or is applied subsequent to another entity’s format.
-
D.
formatBefore
Indicates that one item’s format or formatting must occur or be applied prior to another item’s format or formatting.
-
E.
formatVariantOf
Indicates that one entity is an alternative representation or version of another entity that differs only in format while preserving the same underlying content or meaning.
- F. None of above. chosen
Provenance (4 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 29, 2026, 7:52 p.m.