Triple
T16875648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Froy |
E421291
|
entity |
| Predicate | codeTransmissionMethod |
P7413
|
FINISHED |
| Object | folk tune containing a secret code |
—
|
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: folk tune containing a secret code | Statement: [Miss Froy, codeTransmissionMethod, folk tune containing a secret code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeTransmissionMethod Context triple: [Miss Froy, codeTransmissionMethod, folk tune containing a secret code]
-
A.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
B.
transmissionType
chosen
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
C.
attachmentMethod
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
-
D.
modeOfTransmission
Indicates the method or pathway through which something, typically a disease or information, is passed from one source to another.
-
E.
baseTransmission
Indicates the fundamental or default mode by which something is transmitted or passed from one entity to another.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f646308190b5e277b5f51cd315 |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.