Triple
T13514086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TEDMED |
E322711
|
entity |
| Predicate | sharesContentAs |
P110060
|
FINISHED |
| Object | recorded talks |
—
|
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: recorded talks | Statement: [TEDMED, sharesContentAs, recorded talks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesContentAs Context triple: [TEDMED, sharesContentAs, recorded talks]
-
A.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
B.
sharesStatusWith
Indicates that two entities have the same status or state within a given context.
-
C.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
D.
sharesNetwork
Indicates that two or more entities are connected to and operate within the same network.
-
E.
sharesPlatformWith
Indicates that two entities operate on, are available through, or participate within the same platform or system.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf87ca288190a147fbdb2f90985f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaee128d88190b097be17fdd2f92b |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.