Triple
T5480675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRF |
E123458
|
entity |
| Predicate | MRFCFunction |
P38257
|
FINISHED |
| Object | signaling control of media resources |
—
|
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: signaling control of media resources | Statement: [MRF, MRFCFunction, signaling control of media resources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MRFCFunction Context triple: [MRF, MRFCFunction, signaling control of media resources]
-
A.
PLEXFunction
Indicates a functional or operational role that one entity performs or serves for another within a system or context.
-
B.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
C.
usesFunction
chosen
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
D.
textualFunction
Indicates a functional or structural role that a text segment serves within a larger document or discourse (e.g., title, caption, summary, instruction).
-
E.
formalFunction
Indicates that an entity serves an official or designated role or purpose within a formal structure, system, or context.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.